linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Boldi <a1426z@gawab.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: raid1 does not seem faster
Date: Tue, 3 Apr 2007 16:42:27 +0300	[thread overview]
Message-ID: <200704031642.27701.a1426z@gawab.com> (raw)
In-Reply-To: <46118473.10205@tmr.com>

Bill Davidsen wrote:
> Al Boldi wrote:
> > The problem is that raid1 one doesn't do striped reads, but rather uses
> > read-balancing per proc.  Try your test with parallel reads; it should
> > be faster.
:
:
> It would be nice if reads larger than some size were considered as
> candidates for multiple devices. By setting the readahead larger than
> that value speed increases would be noted for sequential access.

Actually, that's what I thought for a long time too, but as Neil once pointed 
out, for striped reads to be efficient, each chunk should be located 
sequentially, as to avoid any seeks.  This is only possible by introducing 
some offset layout, as in raid10, which infers a loss of raid1's 
single-disk-image compatibility.

What could be feasible, is some kind of an initial burst striped readahead, 
which could possibly improve small reads < (readahead * nr_of_disks).


Thanks!

--
Al


  parent reply	other threads:[~2007-04-03 13:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-01 12:19 raid1 does not seem faster Jan Engelhardt
2007-04-01 12:27 ` Henrik Holst
2007-04-01 12:58 ` Al Boldi
     [not found]   ` <46118473.10205@tmr.com>
2007-04-03 13:42     ` Al Boldi [this message]
2007-04-04 23:11       ` Bill Davidsen
2007-04-05  4:58         ` Iustin Pop
2007-04-05  8:11           ` Justin Piszcz
2007-04-05 15:31             ` Iustin Pop
2007-04-05 15:57               ` Justin Piszcz
2007-04-05 19:19                 ` Bill Davidsen
2007-04-09 10:53             ` Justin Piszcz
2007-04-09 12:17               ` Iustin Pop
2007-04-05 13:45           ` Bill Davidsen
2007-04-05 15:38             ` Iustin Pop

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=200704031642.27701.a1426z@gawab.com \
    --to=a1426z@gawab.com \
    --cc=davidsen@tmr.com \
    --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).