All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Iustin Pop <iusty@k1024.org>, Al Boldi <a1426z@gawab.com>,
	linux-raid@vger.kernel.org
Subject: Re: raid1 does not seem faster
Date: Thu, 05 Apr 2007 15:19:15 -0400	[thread overview]
Message-ID: <46154BB3.3010006@tmr.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0704051156480.23524@p34.internal.lan>

Justin Piszcz wrote:
>
>
> On Thu, 5 Apr 2007, Iustin Pop wrote:
>
>> On Thu, Apr 05, 2007 at 04:11:35AM -0400, Justin Piszcz wrote:
>>>
>>>
>>> On Thu, 5 Apr 2007, Iustin Pop wrote:
>>>
>>>> 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
>>>> -
>>>> To unsubscribe from this list: send the line "unsubscribe 
>>>> linux-raid" in
>>>> the body of a message to majordomo@vger.kernel.org
>>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>>
>>>
>>> Really? I have copied a file from a SW RAID1 (5GB) and I only saw
>>> 60MB/s not the 120MB/s the (RAID1) is capable of to the
>>> destination (which can easily do > 160MB/s sustained read/write).
>>
>> Did you copy it multi-threaded? I said "*multiple-readers* show improved
>> speed" and you said "I copied *one* file". Try copying two files in
>> parallel.
>>
>> I'm doing in two xterms "cat file1 >/dev/null", "cat file2 >/dev/null"
>> and my raid1 shows ~110 MB/s, each drive doing about half.  On file only
>> does about 60 MB/s (this is over a PCI raid controller so the max 110
>> MB/s is a PCI bus limitation).
>>
>> Iustin
>> -
>> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>
> Ah, nope, I only did a single copy, I did not parallelize the operations.
And it would be nice not to have to jump through hoops to get better 
performance... You can implement raid[01] at the user level, too, why 
bother to have it in the kernel? ;-)

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


  reply	other threads:[~2007-04-05 19:19 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
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 [this message]
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=46154BB3.3010006@tmr.com \
    --to=davidsen@tmr.com \
    --cc=a1426z@gawab.com \
    --cc=iusty@k1024.org \
    --cc=jpiszcz@lucidpixels.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 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.