From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Hannes Dorbath <light@theendofthetunnel.de>
Cc: Gabor Gombas <gombasg@sztaki.hu>,
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 07:32:33 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0707180732140.7659@p34.internal.lan> (raw)
In-Reply-To: <469DF8D3.8020908@theendofthetunnel.de>
On Wed, 18 Jul 2007, Hannes Dorbath wrote:
> On 18.07.2007 13:19, Justin Piszcz wrote:
>> For the HW RAID tests (2) at the bottom of the e-mail, no, I did not set
>> nr_requests or use the deadline scheduler.
>>
>> For the SW RAID tests, I applied similar optimizations, I am probably not
>> at the latest firmware. The main thing I wanted to use though was SW RAID
>> because the card itself offers so many ports, however, with write speed
>> being that slow I am not sure its a good idea.
>
> I think what you might be experiencing is that XFS can read su,sw values from
> the MD device and will automatically optimize itself, while it can't do that
> for the HW RAID device. It is absolutely essential to align your file system,
> to prevent implicit reads, needed for parity calculations.
>
> Set su to the stripe size you have configured in your controller (like 128K)
> and sw to 9 (for a 10 disk RAID 5 array).
>
>
> --
> Regards,
> Hannes Dorbath
>
Yes I agree here, but I guess my question is why is SW RAID5 so slow on
the 3ware card?
Justin.
next prev parent reply other threads:[~2007-07-18 11:32 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
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 [this message]
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.0707180732140.7659@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=gombasg@sztaki.hu \
--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).