All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: adfas asd <chimera_god@yahoo.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Disappointing RAID10 Performance
Date: Wed, 21 Oct 2009 19:26:14 -0400	[thread overview]
Message-ID: <4ADF9896.6090201@tmr.com> (raw)
In-Reply-To: <715541.19877.qm@web38803.mail.mud.yahoo.com>

adfas asd wrote:
> --- On Fri, 10/16/09, Rob Becker <Rob.Becker@riverbed.com> wrote:
>   
>>    What command did you use to create your
>> raid-10?
>>     
>
> /
> mdadm --create /dev/md0 --level=raid1 --chunk=256 --raid-disks=2 missing /dev/sdb1
> swap
> mdadm --create /dev/md1 --level=raid10 --layout=o2 --chunk=256 --raid-disks=2 missing /dev/sdb2
> /home
> mdadm --create /dev/md2 --level=raid10 --layout=o2 --chunk=1024 --raid-disks=2 missing /dev/sdb3
> ... then copied files and later added the sda parts to the array. (RAID conversion on live system)
>
>   
No wonder it's slow, you want two far copies, this is more or less 
mirroring with only two drives. Using a large buffer size also helps, 
you hurt your performance by limiting readahead. You can also use the 
'blockdev' command (--setra) to increase your readahead on the array. 
Just going to far should about double your speed, the other things may 
help more.
>   
>>  You might try  
>> running iostat in parallel to see if the read_balancer is
>> properly  
>> balancing the reads between the two disks.
>>     
>
> Don't understand this as I'm a bit of a n00b...
>
>
> --- On Fri, 10/16/09, Tomasz Chmielewski <mangoo@wpkg.org> wrote:
>   
>> If you only use your RAID-10 array for a single "dd
>> if=bigfile of=/dev/null" then yes, it does not give you much
>> over mirroring.
>>
>> If you start using your drives for two "dd if=bigfile[12]
>> of=/dev/null" at the same time, you will notice the
>> difference.
>>     
>
> OK so it was a fallacy to think this would help with large files, unless more than one is involved.
>   

You are misconfigured.

-- 
Bill Davidsen <davidsen@tmr.com>
  Unintended results are the well-earned reward for incompetence.


  reply	other threads:[~2009-10-21 23:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-16 17:32 Disappointing RAID10 Performance adfas asd
2009-10-16 17:36 ` Majed B.
2009-10-16 18:10 ` Rob Becker
2009-10-16 21:05   ` adfas asd
2009-10-21 23:26     ` Bill Davidsen [this message]
2009-10-16 18:30 ` Tomasz Chmielewski
2009-10-17 16:12   ` Asdo
2009-10-17 16:20     ` Tomasz Chmielewski
2009-10-17 21:35     ` Majed B.
2009-10-18 11:01       ` Michael Tokarev
2009-10-16 21:20 ` Christopher Chen
2009-10-18 12:06   ` adfas asd
2009-10-16 21:27 ` Keld Jørn Simonsen
2009-10-17  6:03 ` Leslie Rhorer
2009-10-18 12:17   ` adfas asd
     [not found] <7bc80d500910161433l49cbf599m80310082b6fdaa97@mail.gmail.com>
2009-10-18 12:14 ` adfas asd

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=4ADF9896.6090201@tmr.com \
    --to=davidsen@tmr.com \
    --cc=chimera_god@yahoo.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.