All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mike Galbraith" <EFAULT@gmx.de>
To: "Andrew Morton" <akpm@digeo.com>,
	"Tim Connors" <tconnors@astro.swin.edu.au>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.47 scheduler problems?
Date: Mon, 18 Nov 2002 08:35:56 +0100	[thread overview]
Message-ID: <002e01c28ed5$21f6dd00$6400a8c0@mikeg> (raw)
In-Reply-To: 3DD891D6.93E8E5E4@digeo.com


----- Original Message -----
From: "Andrew Morton" <akpm@digeo.com>
To: "Tim Connors" <tconnors@astro.swin.edu.au>
Cc: <linux-kernel@vger.kernel.org>; "Mike Galbraith" <efault@gmx.de>
Sent: Monday, November 18, 2002 8:08 AM
Subject: Re: 2.5.47 scheduler problems?


> Tim Connors wrote:
> >
> > > I used to be able to wave a window poorly at make -j25 (swapping
heftily),
> > > fairly smoothly at make -j20, and smoothly at make -j15 or below.
This
> > > with no SCHED_RR/SCHED_FIFO.  (I haven't done much testing like
this in
> > > quite a while though)
> >
> > Perhaps you should consider buying an extra 29 CPU's for you
desktop?
> >
>
> No.  He's saying that it used to be OK, but it has got worse.
>
> A much simpler test is to start a big compilation and then madly
> waggle an X window around.  Goes OK for a few seconds, and then
> seizes up quite horridly.  Presumably because the scheduler has
> suddenly decided that the X server has become a "batch" process
> and is scheduling it in a similar manner to the compilation.
>
> If you stop wiggling the window for 5-10 seconds it comes back.
> Presumably because the scheduler has decided that the X server is
> "interactive" again.
>
> When it happens, it's *very* bad.  The mouse cursor doesn't move
> for 0.5-1.0 seconds and then takes great leaps.  It is unusable.

I was watching it this morning, without wiggling, and it seems to update
window content (make output in one and vmstat in another) about every 5
seconds.. very odd looking.

    -Mike


  reply	other threads:[~2002-11-18  7:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-18  6:20 2.5.47 scheduler problems? Mike Galbraith
2002-11-18  6:51 ` Tim Connors
2002-11-18  7:08   ` Andrew Morton
2002-11-18  7:35     ` Mike Galbraith [this message]
2002-11-18  7:29   ` Mike Galbraith
2002-11-18  7:53     ` Tim Connors
2002-11-18 10:52       ` Mike Galbraith
  -- strict thread matches above, loose matches on Subject: below --
2002-11-22  5:41 Jim Houston
2002-11-22 11:07 ` Mike Galbraith
2002-11-22 12:51   ` Mike Galbraith
2002-11-22 14:04     ` Mike Galbraith

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='002e01c28ed5$21f6dd00$6400a8c0@mikeg' \
    --to=efault@gmx.de \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tconnors@astro.swin.edu.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.