linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Hannes Dorbath <light@theendofthetunnel.de>
Cc: linux-ide-arrays@lists.math.uh.edu, xfs@oss.sgi.com,
	linux-raid@vger.kernel.org, linux@vger.kernel.org
Subject: Re: Software RAID5 Horrible Write Speed On 3ware Controller!!
Date: Wed, 18 Jul 2007 12:26:29 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0707181225560.26004@p34.internal.lan> (raw)
In-Reply-To: <469DF039.4040906@theendofthetunnel.de>



On Wed, 18 Jul 2007, Hannes Dorbath wrote:

> On 18.07.2007 12:23, Justin Piszcz wrote:
>> I am sure one of your questions is, well, why use SW RAID5 on the 
>> controller?  Because SW RAID5 is usually much faster than HW RAID5, at 
>> least in my tests:
>
> Though that's no answer to your question, I really can't confirm that. I'm 
> running a 3Ware 9650 with 8x 7200 SATAs in HW RAID 6. Writes are between 
> 340-360MB/sec and reads peak at 430-450MB/sec. That seems to be the absolute 
> possible maximum those drives can deliver. The card even seems to do some 
> really smart stuff, as the read speed is in excess of the physical raw speed 
> of 6 drives.
>
> You have done the usual settings, 3Ware recommends?
>
> echo 64 > /sys/block/sda/queue/max_sectors_kb
> echo 512 > /sys/block/sda/queue/nr_requests
> echo "deadline" > /sys/block/sda/queue/scheduler
> blockdev --setra 16384 /dev/sdX
>
> Have you set the correct su,sw options for XFS?
>
>
> -- 
> Regards,
> Hannes Dorbath
>

I will try these options during future testing and re-visit the speeds of 
regular HW RAID5, thanks!  I know they are part of the 3ware doc and I 
need to re-bench with these.

  reply	other threads:[~2007-07-18 16:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-18 10:23 Software RAID5 Horrible Write Speed On 3ware Controller!! Justin Piszcz
2007-07-18 10:49 ` Hannes Dorbath
2007-07-18 16:26   ` Justin Piszcz [this message]
2007-07-18 17:18     ` Bryan J. Smith
2007-07-18 10:59 ` Al Boldi
2007-07-18 12:01   ` Justin Piszcz
2007-07-18 11:05 ` Gabor Gombas
2007-07-18 11:19   ` Justin Piszcz
2007-07-18 11:26     ` Hannes Dorbath
2007-07-18 11:32       ` Justin Piszcz
2007-07-18 11:37         ` Hannes Dorbath
2007-07-18 11:38           ` Justin Piszcz
2007-07-18 12:51       ` Robin Hill
2007-07-18 14:26         ` Gabor Gombas
2007-07-18 11:17 ` Giuseppe Ghibò
2007-07-18 11:20   ` Justin Piszcz
2007-07-18 17:57   ` Bryan J. Smith
2007-07-18 11:26 ` Sander
2007-07-18 11:35   ` Justin Piszcz
2007-07-18 12:09     ` Sander
2007-07-18 12:19       ` Justin Piszcz
2007-07-18 13:32         ` Sander

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=Pine.LNX.4.64.0707181225560.26004@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=light@theendofthetunnel.de \
    --cc=linux-ide-arrays@lists.math.uh.edu \
    --cc=linux-raid@vger.kernel.org \
    --cc=linux@vger.kernel.org \
    --cc=xfs@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).