From: Max Waterman <davidmaxwaterman+gmane@fastmail.co.uk>
To: linux-raid@vger.kernel.org
Subject: Re: RAID 1 vs RAID 0
Date: Wed, 18 Jan 2006 16:00:03 +0800 [thread overview]
Message-ID: <dqksi3$mf2$5@sea.gmane.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0601180228370.2456-100000@coffee.psychology.mcmaster.ca>
Mark Hahn wrote:
>> They seem to suggest RAID 0 is faster for reading than RAID 1, and I
>> can't figure out why.
>
> with R0, streaming from two disks involves no seeks;
> with R1, a single stream will have to read, say 0-64K from the first disk,
> and 64-128K from the second. these could happen at the same time, and
> would indeed match R0 bandwidth. but with R1, each disk has to seek past
> the blocks being read from the other disk. seeking tends to be slow...
Ah, a good way of putting it...I think I was pretty much there with my
followup message.
Still, it seems like it should be a solvable problem...if you order the
data differently on each disk; for example, in the two disk case,
putting odd and even numbered 'stripes' on different platters [or sides
of platters].
>
>> Clearly, the write performance is worse for RAID 1 than RAID 0 since
>> with RAID 1 that data you are writing at the same time is the same for
>> both drives;
>
> the cost for doing the double writes in R1 is not high, unless you've
> already got a bottleneck somewhere that limits you to talking to one disk
> at a time. for instance, R1 to a pair of disks at 50 MB/s apiece is
> basically trivial for a decent server, since it's about 1% of memory
> bandwidth, and a smallish fraction of even plain old 64x66 PCI.
>
>> array has more than two disks, that would make RAID 1 *faster* than RAID 0.
>
> R1 is not going to be faster than R0 on the same number of disks.
Yeah, I think I see that now.
Thanks.
Max.
>
> regards, mark hahn.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2006-01-18 8:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 5:07 RAID 1 vs RAID 0 Max Waterman
2006-01-18 5:20 ` Max Waterman
2006-01-18 7:40 ` Mark Hahn
2006-01-18 8:00 ` Max Waterman [this message]
2006-01-18 8:40 ` Brad Campbell
2006-01-18 10:33 ` Mario 'BitKoenig' Holbe
2006-01-18 11:43 ` Neil Brown
2006-01-18 13:02 ` John Hendrikx
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='dqksi3$mf2$5@sea.gmane.org' \
--to=davidmaxwaterman+gmane@fastmail.co.uk \
--cc=linux-raid@vger.kernel.org \
/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).