From: "Nico Schümann" <spam@nico22.de>
To: linux-kernel@vger.kernel.org
Subject: CFS not suitable for desktop computers
Date: Sun, 03 May 2009 21:26:09 +0200 [thread overview]
Message-ID: <49FDEFD1.8020608@nico22.de> (raw)
Dear Linux developers,
I have been using Linux for some years now and for me, the best thing
about 2.6 was that Linux ran desktop applications just smoothly. I was
able to compile in the background, while all applications under X11 were
just usable as if the machine was in idle mode. This was due to the
priority of gcc being set to 30, for instance.
Then, somewhere around 2.6.19 or 2.6.21, I do not remember exactly, the
CFS was introduced, which removed all those "latency-based" scheduling
policies. Now that I use 2.6.29 (I did not write earlier because I
though it was a regression issue) I have to say: Linux is not as
perfectly usable as before. End users do not want to experiment with
nice levels and stuff, they just want that the system stays responsible
even if there is a cpu-consuming process in the _background_. For me,
this had been the greatest benefit from using Linux .
Now what can we do, so that foreground applications are smoothly usable
during hard cpu load? Is there any way to restore the old behaviour that
cpu-consuming processes get a lower priority? It had always worked until
this new scheduler was introduced.
Regards,
Nico Schümann
next reply other threads:[~2009-05-03 19:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-03 19:26 Nico Schümann [this message]
2009-05-03 23:24 ` CFS not suitable for desktop computers 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
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=49FDEFD1.8020608@nico22.de \
--to=spam@nico22.de \
--cc=linux-kernel@vger.kernel.org \
/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