linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Iustin Pop <iusty@k1024.org>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Al Boldi <a1426z@gawab.com>, linux-raid@vger.kernel.org
Subject: Re: raid1 does not seem faster
Date: Thu, 5 Apr 2007 06:58:19 +0200	[thread overview]
Message-ID: <20070405045819.GA5525@teal.hq.k1024.org> (raw)
In-Reply-To: <461430B6.9060703@tmr.com>

On Wed, Apr 04, 2007 at 07:11:50PM -0400, Bill Davidsen wrote:
> You are correct, but I think if an optimization were to be done, some 
> balance between the read time, seek time, and read size could be done. 
> Using more than one drive only makes sense when the read transfer time is 
> significantly longer than the seek time. With an aggressive readahead set 
> for the array that would happen regularly.
> 
> It's possible, it just takes the time to do it, like many other "nice" 
> things.

Maybe yes, but why optimise the single-reader case? raid1 already can
read in parallel from the drives when multiple processes read from the
raid1. Optimising the single reader can help in hdparm or other
benchmark cases, but in real life I see very often the total throughput
of a (two drive) raid1 being around two times the throughput of a single
drive.

regards,
iustin

  reply	other threads:[~2007-04-05  4:58 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
2007-04-04 23:11       ` Bill Davidsen
2007-04-05  4:58         ` Iustin Pop [this message]
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=20070405045819.GA5525@teal.hq.k1024.org \
    --to=iusty@k1024.org \
    --cc=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).