From: Peter Rabbitson <rabbit+list@rabbit.us>
To: Peter Grandi <pg@lxra2.for.sabi.co.uk>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Suboptimal raid6 linear read speed
Date: Tue, 22 Jan 2013 01:40:39 +1100 [thread overview]
Message-ID: <20130121144039.GA4103@rabbit.us> (raw)
In-Reply-To: <20732.17741.587765.199649@tree.ty.sabi.co.uk>
Thank you for the thorough reply. While I agree with *most* of what
you say I have a comment and a followup question below.
On Sun, Jan 20, 2013 at 07:28:13PM +0000, Peter Grandi wrote:
> [ ... the original question on 2+2 RAID delivering 2x linear
> transfers of 1x linear transfers ... ]
>
> The original question was based on the (euphemism) very peculiar
> belief that skipping over P/Q blocks has negligible cost.
I was indeed very surprised to find out that the skipping is *not* free.
I am planning to do some research on whether it is possible to use
specific chunksizes so that when laid out on top of the physical media
the "skip penalty" is minimized. This will probably take me a while, but
I will come back to this thread with the results eventually.
> Getting back to RAID, I feel (euphemism) dismayed when I read
> (euphemism) superficialities like:
>
> "raid6 can lose any random 2 drives, while raid10 can't."
>
> because they are based on the (euphemism) disregard of the very
> many differences between the two, and that what matters is the
> level of reliability and performance achievable with the same
> budget. Because ultimately it is reliability/performance per
> budget that matters, not (euphemism) uninformed issues of mere
> geometry.
I am not sure what you are saying... I see raid as a way for me to keep
a higher layer "online", while some of the physical drives fall on the
floor. In the case of 4 drives (very typical for mom&pop+consultant
shops with near-sufficient expertise but far-insufficient funds) a raid6
is the more obvious choice as it provides the array size of 2xdrives,
with reasonable redundancy (*ANY* 2 drives), and reasonable-ish
read/write rates in normal operation. With the prospect of minimizing the
skip-penalty the read rate (which is what matters, again, in most cases)
will go even higher.
By the way "normal operation" is what I am basing my observation on,
because a degraded raid does not run for years without being taken care
of. If it does - someone is doing it wrong. Besides with raid6 the
degradation of operational speeds will be a contributing factor to
repair the array *sooner*.
Compare to raid10, which has better read characteristics, but in order
to reach the "any 2 drives" bounty, one needs to assemble a -l 10 -n 4
-p f3, which isn't... very optimal (mom&pop just went from 2xsize to
1.3xsize).
From your comment above I gather you disagree with this. Can you
elaborate more on the economics of mom&pop installations, and how my
assesment is (euphemism) wrong? :)
Cheers
next prev parent reply other threads:[~2013-01-21 14:40 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 12:33 Suboptimal raid6 linear read speed Peter Rabbitson
2013-01-15 12:45 ` Mikael Abrahamsson
2013-01-15 12:56 ` Peter Rabbitson
2013-01-15 16:13 ` Mikael Abrahamsson
2013-01-15 12:49 ` Phil Turmel
2013-01-15 12:55 ` Peter Rabbitson
2013-01-15 17:09 ` Charles Polisher
2013-01-15 19:57 ` keld
2013-01-16 4:43 ` Charles Polisher
2013-01-16 6:37 ` Tommy Apel Hansen
2013-01-16 9:36 ` keld
2013-01-16 16:09 ` Charles Polisher
2013-01-16 20:40 ` EJ Vincent
2013-01-15 23:17 ` Phil Turmel
2013-01-16 2:48 ` Stan Hoeppner
2013-01-16 2:58 ` Peter Rabbitson
2013-01-16 20:29 ` Stan Hoeppner
2013-01-16 21:20 ` Roy Sigurd Karlsbakk
2013-01-17 15:51 ` Mikael Abrahamsson
2013-01-18 8:31 ` Stan Hoeppner
2013-01-18 9:18 ` Mikael Abrahamsson
2013-01-18 22:56 ` Stan Hoeppner
2013-01-19 7:43 ` Mikael Abrahamsson
2013-01-19 22:48 ` Stan Hoeppner
2013-01-19 23:51 ` Maarten
2013-01-20 0:16 ` Chris Murphy
2013-01-20 0:49 ` Maarten
2013-01-20 1:37 ` Phil Turmel
2013-01-20 9:44 ` Chris Murphy
2013-01-20 6:26 ` Mikael Abrahamsson
2013-01-20 9:39 ` Chris Murphy
2013-01-20 16:55 ` Mikael Abrahamsson
2013-01-20 17:15 ` Chris Murphy
2013-01-20 17:17 ` Mikael Abrahamsson
2013-01-20 17:20 ` Chris Murphy
2013-01-19 23:53 ` Phil Turmel
2013-01-20 9:04 ` Wolfgang Denk
2013-01-20 19:28 ` Peter Grandi
2013-01-20 21:09 ` Mikael Abrahamsson
2013-01-20 21:50 ` Peter Grandi
2013-01-21 5:24 ` Mikael Abrahamsson
2013-01-21 14:40 ` Peter Rabbitson [this message]
2013-01-21 20:32 ` Peter Grandi
2013-01-21 20:55 ` Peter Grandi
2013-01-21 22:00 ` Peter Grandi
2013-01-19 13:21 ` Roy Sigurd Karlsbakk
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=20130121144039.GA4103@rabbit.us \
--to=rabbit+list@rabbit.us \
--cc=linux-raid@vger.kernel.org \
--cc=pg@lxra2.for.sabi.co.uk \
/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).