From: Arjan van de Ven <arjan@infradead.org>
To: Robert Bradbury <robert.bradbury@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Scheduler fails to allow for "niceness" with new/fast processes
Date: Tue, 16 Jun 2009 07:43:04 -0700 [thread overview]
Message-ID: <20090616074304.4e41ae98@infradead.org> (raw)
In-Reply-To: <deaa866a0906160723k78c3c54bv35e2e2406e3d13d1@mail.gmail.com>
On Tue, 16 Jun 2009 10:23:59 -0400
Robert Bradbury <robert.bradbury@gmail.com> wrote:
> I primarily use my system (Gentoo) for 3 tasks: (a) Browsing the web
> related to biomedical research (I may often have dozens of windows and
> hundreds of tabs open in several browsers); (b) Running fairly CPU &
> Disk I/O intensive genetics programs; (c) Performing low priority
> rebuilds of various packages (Gentoo packages, firefox/chrome
> releases, etc.
>
> Now (a) is my top priority -- I want my active browser to get all of
> the CPU if it requires it (fast window/tab opens, quick page reloads &
> redraws, etc.); (b) is of lesser priority and (c) is lowest priority.
> This is on a 2.8 GHz Pentium IV (Prescott) with 3GB of RAM and 12GB
> of swap on two drives.
>
> Now I normally run (c) processes at nice -n 19 to (in theory) get the
> least CPU allocation. But it would appear that this does not work. I
> often experience extremely poor user (esp. browser) performance when
> running package builds. In monitoring the package builds I find that
have you tried running latencytop in this workload to see why you're
really stalling? Latencytop can at least tell you for sure if it's
a scheduler issue or something else...
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2009-06-16 14:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 14:23 Scheduler fails to allow for "niceness" with new/fast processes Robert Bradbury
2009-06-16 14:43 ` Arjan van de Ven [this message]
2009-06-16 14:50 ` Alan Cox
2009-06-17 8:02 ` 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=20090616074304.4e41ae98@infradead.org \
--to=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.bradbury@gmail.com \
/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.