From: Jens Axboe <jens.axboe@oracle.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>, Tejun Heo <htejun@gmail.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Some NCQ numbers...
Date: Mon, 9 Jul 2007 14:26:31 +0200 [thread overview]
Message-ID: <20070709122631.GR5267@kernel.dk> (raw)
In-Reply-To: <Pine.LNX.4.64.0707040621170.32656@p34.internal.lan>
On Wed, Jul 04 2007, Justin Piszcz wrote:
> On Wed, 4 Jul 2007, Michael Tokarev wrote:
>
> > Tejun Heo wrote:
> >> Hello,
> >>
> >> Michael Tokarev wrote:
> >>> Well. It looks like the results does not depend on the
> >>> elevator. Originally I tried with deadline, and just
> >>> re-ran the test with noop (hence the long delay with
> >>> the answer) - changing linux elevator changes almost
> >>> nothing in the results - modulo some random "fluctuations".
> >>
> >> I see. Thanks for testing.
> >
> > Here are actual results - the tests were still running when
> > I replied yesterday.
> >
> > Again, this is Seagate ST3250620AS "desktop" drive, 7200RPM,
> > 16Mb cache, 250Gb capacity. The tests were performed with
> > queue depth = 64 (on mptsas), drive write cache is turned
> > off.
>
> I found AS scheduler to be the premium and best for single-user performance.
>
> You want speed? Use AS.
>
> http://home.comcast.net/~jpiszcz/sched/cfq_vs_as_vs_deadline_vs_noop.html
Hmm, I find your data very weak for such a conclusion. Value of the test
itself withstanding, AS seems to be a lot faster for sequential output
for some reason, yet slower for everything else. Which is odd, deadline
should always be running at the same speed for writeout as AS. The only
real difference should be sequential and random reads.
So allow me to call your results questionable. It also looks like bonnie
(some version) output, I never found bonnie to provide good and
repeatable numbers. tiotest is much better, or (of course) fio.
--
Jens Axboe
next prev parent reply other threads:[~2007-07-09 12:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-28 10:51 Some NCQ numbers Michael Tokarev
2007-06-28 11:01 ` Michael Tokarev
2007-07-03 8:19 ` Tejun Heo
2007-07-03 20:29 ` Michael Tokarev
2007-07-04 1:19 ` Tejun Heo
2007-07-04 9:43 ` Michael Tokarev
2007-07-04 10:22 ` Justin Piszcz
2007-07-04 10:33 ` Justin Piszcz
2007-07-05 19:00 ` Bill Davidsen
2007-07-09 11:07 ` Justin Piszcz
2007-07-09 12:26 ` Jens Axboe [this message]
2007-07-05 19:22 ` Bill Davidsen
2007-07-04 14:40 ` James Bottomley
2007-07-09 12:26 ` Jens Axboe
2007-07-04 15:44 ` Dan Aloni
2007-07-04 16:17 ` Michael Tokarev
2007-07-04 16:44 ` Dan Aloni
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=20070709122631.GR5267@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=htejun@gmail.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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;
as well as URLs for NNTP newsgroup(s).