From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Gabor Gombas <gombasg@sztaki.hu>
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 07:19:10 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0707180718000.7659@p34.internal.lan> (raw)
In-Reply-To: <20070718110525.GF13772@boogie.lpds.sztaki.hu>
On Wed, 18 Jul 2007, Gabor Gombas wrote:
> On Wed, Jul 18, 2007 at 06:23:25AM -0400, Justin Piszcz wrote:
>
>> I recently got a chance to test SW RAID5 using 750GB disks (10) in a RAID5
>> on a 3ware card, model no: 9550SXU-12
>>
>> The bottom line is the controller is doing some weird caching with writes
>> on SW RAID5 which makes it not worth using.
>
> Did you use the settings documented in
> http://www.3ware.com/KB/article.aspx?id=11050 ? Setting nr_requests and
> the deadline scheduler doubled the seq write performance for me. Do you
> have the latest firmware? Firmware updates can improve performance - at
> least for RAID5/6; I somewhat doubt that they care about JBOD
> performance that much...
>
> Gabor
>
> --
> ---------------------------------------------------------
> MTA SZTAKI Computer and Automation Research Institute
> Hungarian Academy of Sciences
> ---------------------------------------------------------
>
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.
Justin.
next prev parent reply other threads:[~2007-07-18 11:19 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 [this message]
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.0707180718000.7659@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=gombasg@sztaki.hu \
--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).