All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: "Rustedt, Florian" <florian.rustedt@smartnet.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Mustn't be RAID 1 and 0 read-performance be similar?
Date: Thu, 09 Aug 2007 17:37:36 -0400	[thread overview]
Message-ID: <46BB8920.9090105@tmr.com> (raw)
In-Reply-To: <735D322AED9CD711BE53000476917CD00281A96B@NT-SERVER-5>

Rustedt, Florian wrote:
> Hello List,
>
> If the speed on RAID 0 is based on reading out in parallel, then it must be
> the same on RAID 1, mustn't it?
>
> On RAID 1, it is possible, to read two blocks in parallel to speed up, too.
>
> I tried to measure this some weeks ago, but i couldn't get over the
> read-performance of a single disk on my raid 1, so that means, that the
> software-raid does not use this easy possibility to speed up?
>   

We've had this discussion before, and the RAID code does not take 
advantage of running reads in parallel to satisfy readahead or anything 
else. I seen it said that this is on a per-thread basis, but a simple 
test suggests that it's on a process basis, setting two threads to read 
alternating 10k blocks as fast as possible ran no faster than a single 
thread. However, running against RAID-10, even a single thread seemed to 
run far faster than the speed of a single drive.

Lightly tested, don't take this as the last word.

-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979


  parent reply	other threads:[~2007-08-09 21:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-09  7:15 Mustn't be RAID 1 and 0 read-performance be similar? Rustedt, Florian
2007-08-09 14:13 ` Andy Smith
2007-08-09 21:37 ` Bill Davidsen [this message]
2007-08-13 14:49 ` Mario 'BitKoenig' Holbe

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=46BB8920.9090105@tmr.com \
    --to=davidsen@tmr.com \
    --cc=florian.rustedt@smartnet.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 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.