From: "Keld Jørn Simonsen" <keld@dkuug.dk>
To: Janek Kozicki <janek_listy@wp.pl>
Cc: linux-raid@vger.kernel.org
Subject: Re: which raid level gives maximum overall speed? (raid-10,f2 vs. raid-0)
Date: Tue, 5 Feb 2008 17:10:36 +0100 [thread overview]
Message-ID: <20080205161036.GA30326@rap.rap.dk> (raw)
In-Reply-To: <20080131015506.GB6617@rap.rap.dk>
On Thu, Jan 31, 2008 at 02:55:07AM +0100, Keld Jørn Simonsen wrote:
> On Wed, Jan 30, 2008 at 11:36:39PM +0100, Janek Kozicki wrote:
> > Keld Jørn Simonsen said: (by the date of Wed, 30 Jan 2008 23:00:07 +0100)
> >
>
> All the raid10's will have double time for writing, and raid5 and raid6
> will also have double or triple writing times, given that you can do
> striped writes on the raid0.
For raid5 and raid6 I think this is even worse. My take is that for
raid5 when you write something, you first read the chunk data involved,
then you read the parity data, then you xor-subtract the data to be
changed, and you xor-add the new data, and then write the new data chunk
and the new parity chunk. In total 2 reads and 2 writes. The read/writes
happen on the same chunks, so latency is minimized. But in essence it is
still 4 IO operations, where it is only 2 writes on raid1/raid10,
that is only half the speed for writing on raid5 compared to raid1/10.
On raid6 this amounts to 6 IO operations, resulting in 1/3 of the
writing speed of raid1/10.
I note in passing that there is no difference between xor-subtract and
xor-add.
Also I assume that you can calculate the parities of both raid5 and
raid6 given the old parities chunks and the old and new data chunk.
If you have to calculate the new parities by reading all the component
data chunks this is going to be really expensive, both in IO and CPU.
For a 10 drive raid5 this would involve reading 9 data chunks, and
making writes 5 times as expensive as raid1/10.
best regards
keld
-
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:[~2008-02-05 16:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 18:21 which raid level gives maximum overall speed? (raid-10,f2 vs. raid-0) Janek Kozicki
2008-01-30 22:00 ` Keld Jørn Simonsen
2008-01-30 22:36 ` Janek Kozicki
2008-01-31 1:55 ` Keld Jørn Simonsen
2008-01-31 14:01 ` Janek Kozicki
2008-02-05 16:10 ` Keld Jørn Simonsen [this message]
2008-02-05 16:54 ` Justin Piszcz
2008-02-05 20:04 ` Keld Jørn Simonsen
2008-02-05 22:28 ` Justin Piszcz
2008-02-05 22:52 ` Janek Kozicki
2008-02-06 9:06 ` Peter Rabbitson
[not found] ` <47A9F96E.7050307@tmr.com>
2008-02-06 22:15 ` Janek Kozicki
2008-02-05 22:55 ` Keld Jørn Simonsen
2008-02-05 22:58 ` Justin Piszcz
2008-01-31 15:30 ` Bill Davidsen
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=20080205161036.GA30326@rap.rap.dk \
--to=keld@dkuug.dk \
--cc=janek_listy@wp.pl \
--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).