9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] system responsiveness
Date: Thu,  2 May 2002 11:11:47 -0400	[thread overview]
Message-ID: <ce065d0e73b0653ab6fe1a4631807d01@plan9.bell-labs.com> (raw)

> I don't recall the details, but while I was playing with
> the scheduler last fall Russ and I found that there was a
> bug with assigning priorities.  Under load the scheduler
> was a real dog; I think Russ subsequently fixed it.  Doing

Presotto put some tweaks in for me.  The processes move
around dynamically (between priority levels) a bit more now.
My particular test case was an mp3 encoder, which yielded the
processor to go to disk just often enough that it wasn't being
penalized for using so much CPU.  The scheduler is more responsive
now to long-term CPU hogs that occasionally schedule, so that
background tasks like mp3enc won't hurt your interactive
performance as much.

> so made the system noticeably snappier.  I also ran into
> some problems with what appeared to be lost clock
> interrupts, but never had the time to track things down
> completely.

This is a really cool bug.  The system would just stop
scheduling other processes, but if you moved the mouse
around that would generate enough interrupts that the
preemptive scheduler would go into effect and get you
going.  Stop the moving the mouse, stop making progress.
We never found it, and all that has been rewritten recently
so maybe it got fixed inadvertently.

Russ


             reply	other threads:[~2002-05-02 15:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-02 15:11 Russ Cox [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-02  8:29 forsyth
2002-05-02  5:18 forsyth
2002-05-02  5:14 plan9
2002-05-02  4:42 rob pike, esq.
2002-05-01 19:49 Sape Mullender
2002-05-01 19:13 forsyth
2002-05-01 19:20 ` Scott Schwartz
2002-05-02  5:05 ` William Josephson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ce065d0e73b0653ab6fe1a4631807d01@plan9.bell-labs.com \
    --to=rsc@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).