From: "J. Ryan Earl" <heretic@clanhk.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Willy Tarreau <willy@w.ods.org>, Jeff Garzik <jgarzik@pobox.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: Linux SATA RAID FAQ
Date: Sat, 14 Aug 2004 16:28:33 -0600 [thread overview]
Message-ID: <411E9211.8090108@clanhk.org> (raw)
In-Reply-To: <1092496912.27156.6.camel@localhost.localdomain>
Alan Cox wrote:
>Be cautious what you measure. One of he problems until you reach PCI-X
>is PCI bandwidth. Thus software md5 can look good but the moment its
>combined with other PCI activity goes down the pan entirely.
>
>
Right, which is why you'd think hardware based RAID would fair better,
the parity information or mirror'd writes would only require one
transfer/transaction across the PCI bus. However, when benchmarking a
3Ware 4-port ide raid controller (7000) we saw 40-50MB/sec read/write on
4x160GB drives raid5. With md raid5 (same controller, HDs, FS, etc) we
saw 100MB/sec read, 60MB/sec write. This was using max 15% CPU on a
2.4GHz Pentium4, with a 32bit/33MHz PCI bus.
>
>
>>When the libata Marvell drivers come out, you'll have a cheap upgrade
>>path for PCI-X boards if you want fast md raid:
>>
>>
>
>Agreed. PCI-X will change a lot of this for boxes that are not very
>cpu/memory limited.
>
>
From the testing I've done, interconnect bandwidth has always been the
limiting factor for the md driver. Using cheap ($~230) PCI-X
motherboards--http://www.supermicro.com/products/motherboard/P4/E7210/P4SCT+.cfm--with
dedicated gigE channels, you can make high density/price and
performance/price NAS type appliances with no bottlenecks. For <$3K you
can build a 2TB NAS server that'll keep a 250MB/s gigE link saturated.
-ryan
next prev parent reply other threads:[~2004-08-14 21:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 6:33 Linux SATA RAID FAQ Jeff Garzik
2004-08-12 7:18 ` Michael Knigge
2004-08-12 11:17 ` Paul Ionescu
2004-08-12 11:34 ` Willy Tarreau
2004-08-14 0:31 ` J. Ryan Earl
2004-08-14 15:21 ` Alan Cox
2004-08-14 22:28 ` J. Ryan Earl [this message]
2004-08-12 18:09 ` Martin Schlemmer
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=411E9211.8090108@clanhk.org \
--to=heretic@clanhk.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@w.ods.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 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).