From: Mike Galbraith <efault@gmx.de>
To: Matthias Dahl <mlkernel@mortal-soul.de>
Cc: Paolo Ornati <ornati@fastwebnet.it>, Jens Axboe <axboe@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: sluggish system responsiveness under higher IO load
Date: Sat, 14 Oct 2006 18:20:46 +0000 [thread overview]
Message-ID: <1160850046.13212.30.camel@Homer.simpson.net> (raw)
In-Reply-To: <200610141639.58374.mlkernel@mortal-soul.de>
Greetings,
On Sat, 2006-10-14 at 16:39 +0200, Matthias Dahl wrote:
> On Friday 06 October 2006 17:58, Paolo Ornati wrote:
>
> > I used to have this type of problem and 2.6.19-rc1 looks much better
> > than 2.6.18.
> >
> > I'm using CONFIG_PREEMPT + CONFIG_PREEMPT_BKL, CFQ i/o scheduler
> > and /proc/sys/vm/swappiness = 20.
>
> I will give 2.6.19 a test in a few weeks when the dust of all the changes have
> settled a bit. :-)
>
> As my Mike Galbraith suggested, I made some tests with renicing the IO
> intensive applications. This indeed makes a hell of a difference. Currently I
> am renicing everything that causes a lot of disk IO to a nice of 19. Even
> though this doesn't fix it completely, the occasional short hangs have become
> less common.
(I probably should have been more verbose in my suggestion;)
What I actually suggested was that you try renicing the application you
were experiencing sluggishness with to -10, and retry your IO
interference test to see if you were experiencing scheduling latency or
something else. For example, if your GL application is using lots of
cpu, it will likely not be classified as interactive, and can end up in
the expired array, at which time an IO task can do a long burst of heavy
cpu usage at interactive status, and keep your application off of the
cpu for quite a while. The intent of renicing your application to -10
was to keep it at interactive status, and above the heavy IO tasks. (if
it sleeps at all that should work. there are other scenarios too, but
less likely than this one)
If running IO at nice 19 more or less fixes your problem, I think we can
assume that you are having scheduling troubles, so the thing to do is to
grab some top snapshots showing cpu distribution during a problem
period.
-Mike
next prev parent reply other threads:[~2006-10-14 17:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-06 10:00 Matthias Dahl
2006-08-06 10:15 ` Andrew Morton
2006-08-06 13:54 ` Matthias Dahl
2006-08-06 19:37 ` Andrew Morton
2006-08-08 15:47 ` Matthias Dahl
2006-08-07 13:48 ` Jens Axboe
2006-08-08 15:56 ` Matthias Dahl
2006-08-08 17:44 ` Matthias Dahl
2006-08-08 19:02 ` Jens Axboe
2006-08-10 12:28 ` Jens Axboe
2006-08-11 11:40 ` Matthias Dahl
2006-08-13 16:15 ` Matthias Dahl
2006-10-06 15:58 ` Paolo Ornati
2006-10-08 14:28 ` Christian
2006-10-08 17:05 ` Jens Axboe
2006-10-08 23:50 ` Jesper Juhl
2006-10-09 5:58 ` Jens Axboe
2006-10-14 14:39 ` Matthias Dahl
2006-10-14 14:57 ` Paolo Ornati
2006-10-14 18:20 ` Mike Galbraith [this message]
2006-09-03 11:15 ` Matthias Dahl
2006-09-15 18:17 ` Jens Axboe
2006-09-24 14:32 ` Matthias Dahl
2006-09-24 20:27 ` 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=1160850046.13212.30.camel@Homer.simpson.net \
--to=efault@gmx.de \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mlkernel@mortal-soul.de \
--cc=ornati@fastwebnet.it \
/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®