From: Christian <christiand59@web.de>
To: linux-kernel@vger.kernel.org
Subject: Sluggish system responsiveness on I/O
Date: Sat, 18 Nov 2006 14:12:29 +0100 [thread overview]
Message-ID: <200611181412.29144.christiand59@web.de> (raw)
Hello lkml!
Im currently testing 2.6.19-rc5-mm1. Everything works really fine except the
little wart with bad multimedia interactivity with a kernel compiling in the
background. So I tried to narrow it down as much
as possible.
I did several find's,dd's and cats in parrallel and watched four instances of
glxgears and also played a little enemy-territory. The interactivity was very
good, in fact no loss of interactivity at all. This was contrary to what I
believed the whole time. The loss of interactivity has nothing to do with
heavy I/O. In fact it happens only when I run a task which is I/O and CPU
heavy at the same time. That means a single kernel compile (with -j1) is able
to harm interactivity with glxgears and enemy-territory, but fully loading my
three disks does no harm at all.
So I tried to nice the make and see what happens:
nice 5 make -j4: Seems to make no difference. Heavy stuttering in glxgears and
et
nice 10 make -j4: Somewhat better but still unusable with et
everything above nice 15 is usable. nice 19 has full interactivity, that means
you can't make out a difference between no load and kernel compile while
playing enemy-territory.
I suspect that it has something to do with the priority boost for I/O hogs.
But if this is a "general" scheduler problem, then why aren't more people
complaining about this?
-Christian
next reply other threads:[~2006-11-18 13:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-18 13:12 Christian [this message]
2006-11-18 13:25 ` Sluggish system responsiveness on I/O Prakash Punnoor
2006-11-18 14:40 ` Christian
2006-11-19 7:51 ` Mike Galbraith
2006-11-19 17:44 ` Lee Revell
2006-11-19 18:34 ` Mike Galbraith
2006-11-22 10:57 ` [rfc patch] " 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=200611181412.29144.christiand59@web.de \
--to=christiand59@web.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 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.