From: Goswin von Brederlow <goswin-v-b@web.de>
To: linux-raid@vger.kernel.org
Subject: Re: raid10 layout for 2xSSDs
Date: Tue, 17 Nov 2009 05:36:24 +0100 [thread overview]
Message-ID: <87tywtlqd3.fsf@frosties.localdomain> (raw)
In-Reply-To: <20091116163102.GB28577@cthulhu.home.robinhill.me.uk> (Robin Hill's message of "Mon, 16 Nov 2009 16:31:03 +0000")
Robin Hill <robin@robinhill.me.uk> writes:
> On Mon Nov 16, 2009 at 04:26:32PM +0100, Goswin von Brederlow wrote:
>
>> What I'm aiming at is that offset might better fit into erase blocks,
>> cause less internal fragmentation on the disk and give better wear
>> leveling. Might improve speed and lifetime. But that is just a
>> thought. Maybe test and do ask Intel (or other vendors) about it.
>>
> I very much doubt this will make any difference. With SSDs you have to
> throw out any preconceptions of internal layout you may have. You have
> absolutely no idea (or control of) where two consecutive blocks will
> actually get written. Fragmentation and seek time are thus irrelevant
> (or uncontrollable anyway).
>
> I don't see how any RAID-10 layout would perform better than another
> with SSDs, unless there's internal optimisations/constraints which
> affect sequential reading from multiple devices. I'm not aware of any
> though - RAID-10 n2 may be the same layout as RAID-1 but it's an
> entirely separate piece of code.
>
> Cheers,
> Robin
Depending on the SSD in question the limiting factor will be the
number of IO operations per second. Some SSDs have shown that they can
write the same number of 1 byte blocks per second as they can write
64k bytes per second. If offset writes 2x 64k but far writes 4x 32k
then far will be half the speed on such a cheap SSD.
MfG
Goswin
next prev parent reply other threads:[~2009-11-17 4:36 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 [this message]
2009-11-16 16:08 ` Christopher Chen
2009-11-16 21:02 ` Kasper Sandberg
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=87tywtlqd3.fsf@frosties.localdomain \
--to=goswin-v-b@web.de \
--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).