From: Lee Revell <rlrevell@joe-job.com>
To: Haoqiang Zheng <haoqiang@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: question about contest benchmark
Date: Tue, 03 May 2005 14:29:59 -0400 [thread overview]
Message-ID: <1115144999.29445.7.camel@mindpipe> (raw)
In-Reply-To: <d6e6e6dd05050311115d256213@mail.gmail.com>
On Tue, 2005-05-03 at 14:11 -0400, Haoqiang Zheng wrote:
> My question is why is the result bad at all? One could certainly
> argue that contest processes shouldn't consume so much CPU time since
> they are considered to be background jobs. But why is kernel compiling
> considered foreground jobs? Why making kernel compiling faster is
> better?
I have reported the same problem before. CPU bound processes like
kernel compiles will sometimes starve interactive processes like my mail
client (Evolution).
Actually, I discovered a horrible performance bug in Evolution
(suboptimal "hide junk" implementation, and searches for "" not properly
optimized away, see evolution-hackers for a rough patch) that was
responsible for the massive CPU suckage.
But, it seems to me that even if an interactive process briefly goes CPU
bound (due to bloat, bugs, or intent), it should still be scheduled
preferentially to a pure CPU bound process like a build.
Lee
next prev parent reply other threads:[~2005-05-03 18:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 18:11 question about contest benchmark Haoqiang Zheng
2005-05-03 18:29 ` Lee Revell [this message]
2005-05-03 20:09 ` Valdis.Kletnieks
2005-05-03 20:45 ` Lee Revell
2005-05-03 21:58 ` Con Kolivas
2005-05-03 22:30 ` Haoqiang Zheng
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=1115144999.29445.7.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=haoqiang@gmail.com \
--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