From: Michael Tokarev <mjt@tls.msk.ru>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: "Dr. David Alan Gilbert" <linux@treblig.org>,
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 19:52:54 +0400 [thread overview]
Message-ID: <467E9356.1030200@msgid.tls.msk.ru> (raw)
In-Reply-To: <Pine.LNX.4.64.0706241021030.12207@p34.internal.lan>
Justin Piszcz wrote:
> Don't forget about max_sectors_kb either (for all drives in the SW RAID5
> array)
>
> max_sectors_kb = 8
> $ dd if=/dev/zero of=file.out6 bs=1M count=10240
> 10737418240 bytes (11 GB) copied, 55.4848 seconds, 194 MB/s
>
> max_sectors_kb = 128
> 10737418240 bytes (11 GB) copied, 22.6298 seconds, 474 MB/s
Well. You're comparing something different. Yes, this
thread is about linux software raid5 in the first place,
but I were commenting about [NT]CQ within a single drive.
Overall, yes, the larger your reads/writes to the drive
becomes, the faster its linear performance is. Yet you
have to consider real workload instead of very synthetic
dd test. It may be good approcsimation of a streaming
video workload (when you feed a large video file over
network or something like that), but even with this,
you probably want to feed several files at once (different
files to different clients), so single-threaded test
here isn't very useful. IMHO anyway, and good for a
personal computer test.
/mjt
next prev parent reply other threads:[~2007-06-24 15:52 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
2007-06-24 14:21 ` Justin Piszcz
2007-06-24 15:52 ` Michael Tokarev [this message]
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=467E9356.1030200@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=carlo@alinoe.com \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
--cc=manoj@io.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;
as well as URLs for NNTP newsgroup(s).