From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Jeff Garzik <jeff@garzik.org>, Carlo Wood <carlo@alinoe.com>,
Tejun Heo <htejun@gmail.com>, Manoj Kasichainula <manoj@io.com>,
linux-kernel@vger.kernel.org,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: SATA RAID5 speed drop of 100 MB/s
Date: Sun, 24 Jun 2007 13:59:57 +0100 [thread overview]
Message-ID: <20070624125957.GA28067@gallifrey> (raw)
In-Reply-To: <467E5C5E.6000706@msgid.tls.msk.ru>
* Michael Tokarev (mjt@tls.msk.ru) wrote:
<snip>
> By the way, I did some testing of various drives, and NCQ/TCQ indeed
> shows some difference -- with multiple I/O processes (like "server"
> workload), IF NCQ/TCQ is implemented properly, especially in the
> drive.
>
> For example, this is a good one:
>
> Single Seagate 74Gb SCSI drive (10KRPM)
>
> BlkSz Trd linRd rndRd linWr rndWr linR/W rndR/W
<snip>
> 1024k 1 83.1 36.0 55.8 34.6 28.2/27.6 20.3/19.4
> 2 45.2 44.1 36.4/ 9.9
> 4 48.1 47.6 40.7/ 7.1
>
> The tests are direct-I/O over whole drive (/dev/sdX), with
> either 1, 2, or 4 threads doing sequential or random reads
> or writes in blocks of a given size. For the R/W tests,
> we've 2, 4 or 8 threads running in total (1, 2 or 4 readers
> and the same amount of writers). Numbers are MB/sec, as
> totals (summary) for all threads.
>
> Especially interesting is the very last column - random R/W
> in parallel. In almost all cases, more threads gives larger
> total speed (I *guess* it's due to internal optimisations in
> the drive -- with more threads the drive has more chances to
> reorder commands to minimize seek time etc).
>
> The only thing I don't understand is why with larger I/O block
> size we see write speed drop with multiple threads.
My guess is that something is chopping them up into smaller writes.
> And in contrast to the above, here's another test run, now
> with Seagate SATA ST3250620AS ("desktop" class) 250GB
> 7200RPM drive:
>
> BlkSz Trd linRd rndRd linWr rndWr linR/W rndR/W
<snip>
> 1024k 1 78.4 34.1 33.5 24.6 19.6/19.5 16.0/12.7
> 2 33.3 24.6 15.4/13.8
> 4 34.3 25.0 14.7/15.0
>
<snip>
> And second, so far I haven't seen a case where a drive
> with NCQ/TCQ enabled works worse than without. I don't
> want to say there aren't such drives/controllers, but
> it just happen that I haven't seen any.)
Yes you have - the random writes with large blocks and 2 or 4 threads
is significantly better for your non-NCQ drive; and getting more
significant as you add more threads - I'm curious what happens
on 8 threads or more.
Dave
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux on Alpha,68K| Happy \
\ gro.gilbert @ treblig.org | MIPS,x86,ARM,SPARC,PPC & HPPA | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
next prev parent reply other threads:[~2007-06-24 12:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070620224847.GA5488@alinoe.com>
[not found] ` <4679B2DE.9090903@garzik.org>
[not found] ` <20070622214859.GC6970@alinoe.com>
2007-06-23 7:03 ` SATA RAID5 speed drop of 100 MB/s Jeff Garzik
2007-06-23 7:54 ` Tejun Heo
2007-06-23 12:53 ` Carlo Wood
2007-06-23 17:30 ` Bartlomiej Zolnierkiewicz
2007-06-23 22:43 ` Jeff Garzik
2007-06-24 11:58 ` Michael Tokarev
2007-06-24 12:59 ` Dr. David Alan Gilbert [this message]
2007-06-24 14:21 ` Justin Piszcz
2007-06-24 15:52 ` Michael Tokarev
2007-06-24 16:59 ` Justin Piszcz
2007-06-24 22:07 ` Carlo Wood
2007-06-24 23:46 ` Mark Lord
2007-06-25 0:23 ` Patrick Mau
2007-06-24 15:48 ` Michael Tokarev
2007-07-05 22:12 ` Phillip Susi
2007-06-24 0:54 ` Eyal Lebedinsky
2007-06-24 9:01 Mikael Pettersson
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=20070624125957.GA28067@gallifrey \
--to=linux@treblig.org \
--cc=carlo@alinoe.com \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manoj@io.com \
--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).