From: "Mike Galbraith" <EFAULT@gmx.de>
To: "Tim Connors" <tconnors@astro.swin.edu.au>,
<linux-kernel@vger.kernel.org>
Subject: Re: 2.5.47 scheduler problems?
Date: Mon, 18 Nov 2002 08:29:57 +0100 [thread overview]
Message-ID: <001201c28ed4$4c4079a0$6400a8c0@mikeg> (raw)
In-Reply-To: slrn-0.9.7.4-16621-21084-200211181750-j.$random.luser@swin.edu.au
----- Original Message -----
From: "Tim Connors" <tconnors@astro.swin.edu.au>
To: <linux-kernel@vger.kernel.org>; "Mike Galbraith" <efault@gmx.de>
Sent: Monday, November 18, 2002 7:51 AM
Subject: Re: 2.5.47 scheduler problems?
> In linux.kernel, you wrote:
> > Greetings,
> >
> > For testing swap throughput, I like to run make -j30 bzImage on my
500Mhz
> > PIII w. 128Mb ram. For testing interactivity, I fire up KDE, start
a
> > smaller make -j, grab a window, and wave it around.
> >
> > With 2.4.20rc2+rc1aa1, running a -j10 build (not swapping) is very
very
> > bad. However, if I set all tasks in the system to SCHED_FIFO or
SCHED_RR
> > prior to this light make -j, I have a ~pretty smooth system.
> >
> > If I do the same in 2.5.47, I have no control of my box. Setting
all tasks
> > to SCHED_FIFO or SCHED_RR prior to starting make -j10 bzImage, I can
regain
> > control, but interactivity under load is basically not present.
>
> Funny that.
>
> > 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?
I have neither the need for 30 CPUs, nor the cash to pay for such a
beast :)
I gather you think my test is silly?
-Mike
next prev parent reply other threads:[~2002-11-18 7:28 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
2002-11-18 7:29 ` Mike Galbraith [this message]
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='001201c28ed4$4c4079a0$6400a8c0@mikeg' \
--to=efault@gmx.de \
--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.