From: Peter Zijlstra <peterz@infradead.org>
To: "Nico Schümann" <spam@nico22.de>
Cc: linux-kernel@vger.kernel.org, Mike Galbraith <efault@gmx.de>
Subject: Re: CFS not suitable for desktop computers
Date: Wed, 06 May 2009 10:03:40 +0200 [thread overview]
Message-ID: <1241597020.11251.82.camel@twins> (raw)
In-Reply-To: <49FF06D0.80109@nico22.de>
On Mon, 2009-05-04 at 17:16 +0200, Nico Schümann wrote:
> Thank you Ray Lee and Mike Galbraith for your responses, I ran the
> script and attached its gathered information.
>
> Mike Galbraith wrote:
> > How hard is hard? Can you describe the loads you're having trouble
> > with, and the hardware you're running them on?
> >
> >
> I could reproduce "hard" load by just compiling the linux kernel, make
> -j3 while reading mails with Thunderbird, which is not that hard
> foreground load. Thunderbird starts reacting really slowly while compiling.
Right, such a load will leave your thunderbird about 25% of the cpu. I
think its fair to expect it to be slower, but it should still be
workable.
I used to test CFS on my 1.2GHz laptop with 512M and a make -j5. That
would result in a slow but steady system. With steady I mean the latency
was pretty constant.
The O(1) scheduler would utterly mess this up, it would be fast, until
the desktop bloat took enough cpu time and then it would starve a while,
etc..
The thing is, we really cannot go about guessing, its too easy to guess
wrong. If you know its a background task, nice it.
alias make='nice make'
and you're done.
prev parent reply other threads:[~2009-05-06 8:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-03 19:26 CFS not suitable for desktop computers Nico Schümann
2009-05-03 23:24 ` Ray Lee
[not found] ` <1241424835.26855.102.camel@marge.simson.net>
2009-05-04 15:16 ` Nico Schümann
2009-05-04 17:59 ` Mike Galbraith
2009-05-04 21:01 ` Chris Friesen
2009-05-05 5:42 ` Mike Galbraith
2009-05-05 7:51 ` Mike Galbraith
2009-05-06 8:03 ` Peter Zijlstra [this message]
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=1241597020.11251.82.camel@twins \
--to=peterz@infradead.org \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=spam@nico22.de \
/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