All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keld Simonsen <keld@keldix.com>
To: Neil Brown <neilb@suse.de>
Cc: Gilad Arnold <arnold@cs.berkeley.edu>,
	Bill Davidsen <davidsen@tmr.com>, Roman Mamedov <roman@rm.pp.ru>,
	linux-raid@vger.kernel.org
Subject: Re: migrating from RAID5 to RAID10
Date: Fri, 18 Jun 2010 10:40:28 +0200	[thread overview]
Message-ID: <20100618084028.GA23230@rap.rap.dk> (raw)
In-Reply-To: <20100618083053.7df5248b@notabene.brown>

On Fri, Jun 18, 2010 at 08:30:53AM +1000, Neil Brown wrote:
> 
> 2-drive RAID10 f2  would be expected to provide better read throughput
> (possibly twice as fast) at some cost to write throughput.  For many people
> this is a worthwhile trade-off.  So it might be better for you.
> Read throughput would degraded down to write throughput (i.e. slower than
> RAID1) if the RAID10 were degraded.

The slowdown of write thruput is on the raw raid, and on file systems
without elevator algorithms. If you employ a file system with an
elevator algorithm, then there will be no noticeable slowdown for
writes, as witnessed by many benchmarks.

best regards
keld

  reply	other threads:[~2010-06-18  8:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-09 15:11 migrating from RAID5 to RAID10 Gilad Arnold
2010-06-10 18:52 ` Roman Mamedov
2010-06-10 19:58   ` Gilad Arnold
2010-06-10 22:11     ` Drew
2010-06-10 22:21       ` Drew
2010-06-10 22:30         ` Gilad Arnold
2010-06-10 22:26       ` Gilad Arnold
2010-06-16 15:54     ` Bill Davidsen
2010-06-16 18:30       ` Gilad Arnold
2010-06-16 20:15         ` Gilad Arnold
2010-06-17  1:59           ` Bill Davidsen
2010-06-16 21:26       ` Neil Brown
2010-06-17 17:44         ` Gilad Arnold
2010-06-17 22:30           ` Neil Brown
2010-06-18  8:40             ` Keld Simonsen [this message]
2010-06-21 22:09               ` Neil Brown
2010-06-17 22:46           ` Gilad Arnold
2010-06-18  2:39             ` Neil Brown
2010-06-18  4:01               ` Gilad Arnold

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=20100618084028.GA23230@rap.rap.dk \
    --to=keld@keldix.com \
    --cc=arnold@cs.berkeley.edu \
    --cc=davidsen@tmr.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=roman@rm.pp.ru \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.