From: Bill Davidsen <davidsen@tmr.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: Thu, 05 Jul 2007 15:00:38 -0400 [thread overview]
Message-ID: <468D3FD6.7060607@tmr.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0707040631370.32656@p34.internal.lan>
Justin Piszcz wrote:
>
>
> On Wed, 4 Jul 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
>>
>>
>
> Does not include noop-- tested the main three though, renamed :)
>
> http://home.comcast.net/~jpiszcz/sched/cfq_vs_as_vs_deadline.html
>
> And for the archives:
>
> p34-cfq,15696M,77114.3,99,311683,55.3333,184947,38.6667,79842.7,99,524065,41.3333,634.033,0.333333,16:100000:16/64,1043.33,8.33333,4419.33,11.6667,2942,17.3333,1178,10.3333,4192.67,12.3333,2619.33,19
>
> p34-as,15696M,76202.3,99,443103,85,189716,34.6667,79552,99,507271,39.6667,607.067,0,16:100000:16/64,1153,10,13434,36,2769.67,16.3333,1201.67,10.6667,3951.33,12,2665.67,19
>
> p34-deadline,15696M,76933.3,98.6667,386852,72,183016,29.6667,79530.7,99,512082,39.6667,678.567,0,16:100000:16/64,1230.33,10.3333,12349,32.3333,2945,17.3333,1258,11,8183,22.3333,2867,20.3333
>
I looked at these before, did you really run with a chunk size of just
under 16GB, or does "15696M" have some inobvious meaning?
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
next prev parent reply other threads:[~2007-07-09 11:18 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 [this message]
2007-07-09 11:07 ` Justin Piszcz
2007-07-09 12:26 ` Jens Axboe
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=468D3FD6.7060607@tmr.com \
--to=davidsen@tmr.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 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.