From: Kasper Sandberg <postmaster@metanurb.dk>
To: Christopher Chen <muffaleta@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: raid10 layout for 2xSSDs
Date: Mon, 16 Nov 2009 22:02:53 +0100 [thread overview]
Message-ID: <1258405373.31633.49.camel@localhost> (raw)
In-Reply-To: <7bc80d500911160808o4ca4d335gdeeb50fff61b2149@mail.gmail.com>
On Mon, 2009-11-16 at 08:08 -0800, Christopher Chen wrote:
> On Mon, Nov 16, 2009 at 6:29 AM, Kasper Sandberg <postmaster@metanurb.dk> wrote:
> > Hello.
> >
> > I've been wanting to create a raid10 array of two SSDs, and I am
> > currently considering the layout.
> >
> > As i understand it, near layout is similar to raid1, and will only
> > provide a speedup if theres 2 reads at the same time, not a single
> > sequential read.
> >
> > so the choice is really between far and offset. As i see it, the
> > difference is, that offset tries to reduce the seeking for writing
> > compared to far, but that if you dont consider the seeking penalty,
> > average sequential write speed across the entire array should be roughly
> > the same with offset and far, with offset perhaps being a tad more
> > "stable", is this a correct assumption? if it is, that would mean offset
> > provides a higher "garantueed" speed than far, but with a lower maximum
> > speed.
>
> Do you plan to have more than two devices in the array? Raid 10 isn't
no
> magic. If you don't have more than do devices, I suppose your seek
> time might be half for reads (and higher for writes), but you won't be
> able to do any striping.
>
> I'm a bit confused as to the number of people popping in recently
> wanting to run raid 10 on two disk "arrays".
to get the doubled singlestream sequential read performance..
>
> cc
>
next prev parent reply other threads:[~2009-11-16 21:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 14:29 raid10 layout for 2xSSDs Kasper Sandberg
2009-11-16 15:26 ` Goswin von Brederlow
2009-11-16 16:13 ` Keld Jørn Simonsen
2009-11-17 4:34 ` Goswin von Brederlow
2009-11-17 15:05 ` Kasper Sandberg
2009-11-16 16:31 ` Robin Hill
2009-11-16 16:38 ` Christopher Chen
2009-11-16 16:52 ` Robin Hill
2009-11-17 4:36 ` Goswin von Brederlow
2009-11-16 16:08 ` Christopher Chen
2009-11-16 21:02 ` Kasper Sandberg [this message]
2009-11-16 21:19 ` Majed B.
2009-11-16 21:33 ` Kasper Sandberg
2009-11-17 4:46 ` Goswin von Brederlow
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=1258405373.31633.49.camel@localhost \
--to=postmaster@metanurb.dk \
--cc=linux-raid@vger.kernel.org \
--cc=muffaleta@gmail.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).