From: "" <spam@nico22.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Re: CFS not suitable for desktop computers
Date: Tue, 5 May 2009 16:16:32 +0200 (CEST) [thread overview]
Message-ID: <20090505141633.0D90ED040@mail.udag.de> (raw)
On Mon, 2009-05-04 at 15:01 -0600, Chris Friesen wrote:
> I wonder if this could be related to I/O rather than the task scheduler
> proper.
> That's something I was wondering as well, particularly when I noticed
> he's using data=journal and anticipatory io-scheduler.
I will try with different schedulers tonight.
On Tue, 2009-05-05 at 07:42 +0200, Mike Galbraith wrote:
> I have an old P4 lying about (has X candy). I'll update it and try some
> UP testing. Can't test Thunderbird though.
It is not only Thunderbird, which does not have much cpu usage for itself. This laggy behaviour is also noticible by just switching some terminal windows (I use gnome-terminal, again, it for itself does not cause much cpu usage nor disk i/o), minimizing them and so on.
If I set the priority of make -j3 to -n19, the problem vanishes, so I expected the scheduler to be to blame.
Again, thank you all for your efforts :-)
Nico
reply other threads:[~2009-05-05 14:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090505141633.0D90ED040@mail.udag.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
all inboxes | Powered by JetHome®