From: Jens Axboe <jens.axboe@oracle.com>
To: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: tiobench read 50% regression with 2.6.30-rc1
Date: Fri, 10 Apr 2009 09:26:01 +0200 [thread overview]
Message-ID: <20090410072600.GP5178@kernel.dk> (raw)
In-Reply-To: <1239330541.2567.779.camel@ymzhang>
On Fri, Apr 10 2009, Zhang, Yanmin wrote:
> On Thu, 2009-04-09 at 11:57 +0200, Jens Axboe wrote:
> > On Thu, Apr 09 2009, Zhang, Yanmin wrote:
> > > Comparing with 2.6.29's result, tiobench (read) has about 50% regression
> > > with 2.6.30-rc1 on all my machines. Bisect down to below patch.
> > >
> > > b029195dda0129b427c6e579a3bb3ae752da3a93 is first bad commit
> > > commit b029195dda0129b427c6e579a3bb3ae752da3a93
> > > Author: Jens Axboe <jens.axboe@oracle.com>
> > > Date: Tue Apr 7 11:38:31 2009 +0200
> > >
> > > cfq-iosched: don't let idling interfere with plugging
> > >
> > > When CFQ is waiting for a new request from a process, currently it'll
> > > immediately restart queuing when it sees such a request. This doesn't
> > > work very well with streamed IO, since we then end up splitting IO
> > > that would otherwise have been merged nicely. For a simple dd test,
> > > this causes 10x as many requests to be issued as we should have.
> > > Normally this goes unnoticed due to the low overhead of requests
> > > at the device side, but some hardware is very sensitive to request
> > > sizes and there it can cause big slow downs.
> > >
> > >
> > >
> > > Command to start the testing:
> > > #tiotest -k0 -k1 -k3 -f 80 -t 32
> > >
> > > It's a multi-threaded program and starts 32 threads. Every thread does I/O
> > > on its own 80MB file.
> The files should be created before the testing and pls. drop page caches
> by "echo 3 >/proc/sys/vm/drop_caches" before testing.
>
> >
> > It's not a huge surprise that we regressed there. I'll get this fixed up
> > next week. Can you I talk you into trying to change the 'quantum' sysfs
> > variable for the drive? It's in /sys/block/xxx/queue/iosched where xxx
> > is your drive(s). It's set to 4, if you could try progressively larger
> > settings and retest, that would help get things started.
> I tried 4,8,16,64,128 and didn't find result difference.
OK, that's good. I'm away from the source atm, but I think I know what
is going on. We need to kick the queue for anything but the first queued
request. I'll get it fixed up next week.
--
Jens Axboe
next prev parent reply other threads:[~2009-04-10 7:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 8:29 Zhang, Yanmin
2009-04-09 9:57 ` Jens Axboe
2009-04-10 2:29 ` Zhang, Yanmin
2009-04-10 7:26 ` Jens Axboe [this message]
2009-04-14 12:14 ` Jens Axboe
2009-04-15 1:27 ` Zhang, Yanmin
2009-04-15 6:27 ` Jens Axboe
2009-04-15 4:07 ` Jeff Moyer
2009-04-15 6:26 ` Jens Axboe
2009-04-15 11:25 ` Jeff Moyer
2009-04-15 11:30 ` Jens Axboe
2009-04-15 12:00 ` Jeff Moyer
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=20090410072600.GP5178@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yanmin_zhang@linux.intel.com \
/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
Powered by JetHome