From: Thomas Fjellstrom <tfjellstrom@shaw.ca>
To: Andre Tomt <andre@tomt.net>
Cc: Michael Evans <mjevans1983@gmail.com>,
Roger Heflin <rogerheflin@gmail.com>,
Matt Tehonica <matt.tehonica@mac.com>,
linux-raid@vger.kernel.org
Subject: Re: Typical RAID5 transfer speeds
Date: Sun, 20 Dec 2009 09:03:44 -0700 [thread overview]
Message-ID: <200912200903.44435.tfjellstrom@shaw.ca> (raw)
In-Reply-To: <4B2E3A54.5050009@tomt.net>
On Sun December 20 2009, Andre Tomt wrote:
> On 20.12.2009 10:55, Thomas Fjellstrom wrote:
> > While the driver support isn't "perfect"*, I have an AOC-SASLP-MV8, a 2
> > port SAS 4x PCI-e card. (with SAS->SATA converters, its an 8 port SATA
> > card)
> >
> > When I was running some tests on individual drives, and watching
> > iostat, I saw over 500MB/s combined throughput, and that was with only
> > 5 drives. Theoretically it should be capable of 1GB/s given its a x4
> > card. Theoretically.
> >
> > At the very least, the card should be more than capable of providing
> > enough bandwidth for all 8 ports to be filled with regular mechanical
> > hard drives (sans port expanders).
>
> Having tried it connected directly to the north bridge, it seems to top
> out at ~650-700MB/s (also using Windows driver). Which is not too bad
> for a pcie 1.0 x4 card, but unfortunatly will only manage to saturate
> about ~5 modern mechanical drives (currently at 120-130MB/s each for
> SATA 7200rpm), if high sequential performance is all you're looking for.
>
> Currently I solved that by having 4 drives from the array on that card,
> and populating the last four ports with with drives that are seldomly
> used and when used get mostly random i/o but still needs a port ;-)
>
> Still good value for money, indeed.
I tried it on windows, and the tests were abysmal. worse than anything linux
gave. Maybe it was windows's dynamic disks raid sucking, but it was
horrible. I ran a disk benchmark test on it, and the whole suite of tests
should have been able to finish after 12 hours, but after about 24, it
wasn't even done the first read test.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Thomas Fjellstrom
tfjellstrom@shaw.ca
next prev parent reply other threads:[~2009-12-20 16:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-19 0:37 Typical RAID5 transfer speeds Matt Tehonica
2009-12-19 1:05 ` Bernd Schubert
2009-12-19 8:30 ` Thomas Fjellstrom
2009-12-19 9:38 ` Michael Evans
2009-12-19 11:43 ` John Robinson
2009-12-19 19:18 ` Leslie Rhorer
2009-12-21 13:06 ` Goswin von Brederlow
2009-12-19 21:35 ` Roger Heflin
2009-12-20 4:21 ` Michael Evans
2009-12-20 9:55 ` Thomas Fjellstrom
2009-12-20 14:53 ` Andre Tomt
2009-12-20 16:03 ` Thomas Fjellstrom [this message]
2009-12-20 18:28 ` Roger Heflin
2009-12-21 1:18 ` Michael Evans
2009-12-21 1:50 ` Richard Scobie
2009-12-21 11:30 ` Asdo
2009-12-21 18:28 ` Richard Scobie
2009-12-20 10:04 ` Erwan MAS
2009-12-20 10:31 ` Keld Jørn Simonsen
2009-12-20 15:25 ` Andre Tomt
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=200912200903.44435.tfjellstrom@shaw.ca \
--to=tfjellstrom@shaw.ca \
--cc=andre@tomt.net \
--cc=linux-raid@vger.kernel.org \
--cc=matt.tehonica@mac.com \
--cc=mjevans1983@gmail.com \
--cc=rogerheflin@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;
as well as URLs for NNTP newsgroup(s).