From: Jens Axboe <jens.axboe@oracle.com>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Christian <christiand59@web.de>, linux-kernel@vger.kernel.org
Subject: Re: sluggish system responsiveness under higher IO load
Date: Mon, 9 Oct 2006 07:58:25 +0200 [thread overview]
Message-ID: <20061009055825.GC8814@kernel.dk> (raw)
In-Reply-To: <9a8748490610081650q26511b89s4e694f841803cda1@mail.gmail.com>
On Mon, Oct 09 2006, Jesper Juhl wrote:
> On 08/10/06, Jens Axboe <jens.axboe@oracle.com> wrote:
> >On Sun, Oct 08 2006, Christian wrote:
> >> Am Freitag, 6. Oktober 2006 17:58 schrieb Paolo Ornati:
> >> > On Sun, 13 Aug 2006 18:15:12 +0200
> >> >
> >> > Matthias Dahl <mlkernel@mortal-soul.de> wrote:
> >> > > Just let me know once you got them, so I can safely delete them
> >again.
> >> > >
> >> > > At the moment, I am trying without preemption but for example doing a
> >> > > untar kernel sources still results in sluggish system
> >responsiveness. :-(
> >> >
> >> > 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.
> >>
> >>
> >> Which change in the new kernel has made it better? I was following the
> >lkml
> >> very close and didn't see any change that could have fixed that problem.
> >
> >There is a substantial CFQ update, so it could be that. Or it could be
> >something unrelated of course, I didn't check if eg the cpu scheduler
> >changed much. Or vm :-)
> >
> >--
> >Jens Axboe
> >
> I want to chime in here and let you know that I've experienced
> something similar.
>
> I'm using CFQ as my default I/O schedular.
> Since 2.6.18-git<something_I'm_not_sure_of> I've experienced that when
> doing heavy (or even not so heave) disk I/O my system gets very
> sluggish. Observable by the fact that my mouse pointer in X "jumps"
> which it never did before, and switching windows I can see the new
> window repaint slowly whereas earlier it would just snap onto the
> screen.
You should verify that this is CFQ related by booting into the same
kernel with elevator=deadline (or anticipatory) and attempt to reproduce
it, then reboot with CFQ and make sure it reproduces again.
Having profiles of the sluggish period would also be very interesting,
regardless of the outcome of the above test.
--
Jens Axboe
next prev parent reply other threads:[~2006-10-09 5:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-06 10:00 sluggish system responsiveness under higher IO load 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 [this message]
2006-10-14 14:39 ` Matthias Dahl
2006-10-14 14:57 ` Paolo Ornati
2006-10-14 18:20 ` Mike Galbraith
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=20061009055825.GC8814@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=christiand59@web.de \
--cc=jesper.juhl@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