From: Lee Revell <rlrevell@joe-job.com>
To: Valdis.Kletnieks@vt.edu
Cc: Haoqiang Zheng <haoqiang@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: question about contest benchmark
Date: Tue, 03 May 2005 16:45:57 -0400 [thread overview]
Message-ID: <1115153157.29619.33.camel@mindpipe> (raw)
In-Reply-To: <200505032009.j43K9qQJ023179@turing-police.cc.vt.edu>
On Tue, 2005-05-03 at 16:09 -0400, Valdis.Kletnieks@vt.edu wrote:
> On Tue, 03 May 2005 14:29:59 EDT, Lee Revell said:
>
> > 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.
>
> So you want it to schedule that big image (Evolution) that's already used 5
> minutes of CPU since it started (this morning, admittedly) in preference to
> that cc1 process that will be gone before it's used 2 seconds of CPU, plus all
> the disk I/O that cc1 performs (hopefully the cache will help here, but it may
> indeed go to disk to read the source files)?
>
Yes. Almost no one will notice whether that build took 2 or 4 seconds.
But a few seconds is an eternity when you are staring at a blank pane,
waiting for it to render the message list. And I found that when
waiting for the message list to render, backgrounding the build causes
it to render in a second or two, while if I just wait for it it might
take 20 seconds. This implies that the scheduler could do the same
thing.
Anyway, this was not a great example, as the problem turned out to be an
application bug. If I can find a non-pathological case that
demonstrates a scheduler problem, I'll post it.
Lee
next prev parent reply other threads:[~2005-05-03 20:46 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
2005-05-03 20:09 ` Valdis.Kletnieks
2005-05-03 20:45 ` Lee Revell [this message]
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=1115153157.29619.33.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=Valdis.Kletnieks@vt.edu \
--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 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.