mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Lars Roland <lroland@gmail.com>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Poor Software RAID-0 performance with 2.6.14.2
Date: Tue, 22 Nov 2005 08:56:45 +1100	[thread overview]
Message-ID: <17282.17053.19267.253430@cse.unsw.edu.au> (raw)
In-Reply-To: message from Lars Roland on Monday November 21

On Monday November 21, lroland@gmail.com wrote:
> I have created a stripe across two 500Gb disks located on separate IDE
> channels using:
> 
> mdadm -Cv /dev/md0 -c32 -n2 -l0 /dev/hdb /dev/hdd
> 
> the performance is awful on both kernel 2.6.12.5 and 2.6.14.2 (even
> with hdparm and blockdev tuning), both bonnie++ and hdparm (included
> below) shows a single disk operating faster than the stripe:
> 
> ----
> dkstorage01:~# hdparm -t /dev/md0
> /dev/md0:
>  Timing buffered disk reads:  182 MB in  3.01 seconds =  60.47 MB/sec
> 
> dkstorage02:~# hdparm -t /dev/hdc1
> /dev/hdc1:
> Timing buffered disk reads:  184 MB in  3.02 seconds =  60.93 MB/sec
> ----

Could you try hdparm tests on the two drives in parallel?
   hdparm -t /dev/hdb & hdparm -t /dev/hdd

It could be that the controller doesn't handle parallel traffic very
well.


> 
> I am aware of cpu overhead with software raid but such a degradation
> should not be the case with raid 0, especially not when the OS is
> located on a separate SCSI disk - the IDE disks should just be ready
> to work.

raid0 has essentially 0 cpu overhead.  It would be maybe a couple of
hundred instructions which would be lost in the noise.  It just
figures out which drive each request should go to, and directs it
there.


> 
> There have been some earlier reporting on this problem but they all
> seam to end more and less inconclusive (here is one
> http://kerneltrap.org/node/4745). Some people favors switching to
> dmraid with device mapper, is this the de facto standard today ?
> 

The kerneltrap reference is about raid5.
raid5 is implemented very differently to raid0.

It might be worth experimenting with different read-ahead values using
the 'blockdev' command.  Alternately use a larger chunk size.

I don't think there is a de facto standard.  Many people use md.  Many
use dm.  

NeilBrown

  parent reply	other threads:[~2005-11-21 21:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-21 20:31 Lars Roland
2005-11-21 20:47 ` Lennart Sorensen
2005-11-21 21:58   ` Neil Brown
2005-11-22  9:46   ` Lars Roland
2005-11-21 21:56 ` Neil Brown [this message]
2005-11-22 10:04   ` Lars Roland
2005-11-22  8:29 ` Helge Hafting
2005-11-22 17:26 ` Bill Davidsen
2005-11-22 18:23   ` Paul Clements
2005-11-22 21:39     ` Bill Davidsen

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=17282.17053.19267.253430@cse.unsw.edu.au \
    --to=neilb@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lroland@gmail.com \
    /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

all inboxes | Powered by JetHome®