From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Andrew Klaassen <clawsoon@yahoo.com>
Cc: Joshua Baker-LePain <jlb17@duke.edu>,
linux-ide-arrays@lists.math.uh.edu, linux-raid@vger.kernel.org
Subject: Re: 3ware 9650 tips
Date: Sat, 14 Jul 2007 12:18:12 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0707141215200.3534@p34.internal.lan> (raw)
In-Reply-To: <240460.11630.qm@web60012.mail.yahoo.com>
On Sat, 14 Jul 2007, Andrew Klaassen wrote:
> --- Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
>
>> 03:00.0 RAID bus controller: Silicon Image, Inc. SiI
>> 3132 Serial ATA Raid
>> II Controller (rev 01)
>>
>> $19.99 2 port SYBA cards (Silicon Image 3132s)
>>
>> http://www.directron.com/sdsa2pex2ir.html
>
> Cool, thanks.
>
> What are your bonnie++ rewrite numbers?
>
> Andrew
3 runs:
p34,16G,77169,99,413276,80,155348,26,78932,99,535482,41,607.0,0,16:100000:16/64,1500,12,4886,15,1790,16,1821,17,6081,19,2159,19
p34,16G,77659,99,451593,87,167267,28,79058,99,584310,45,613.1,0,16:100000:16/64,1843,15,6006,31,1325,11,1204,12,3629,12,3324,31
p34,16G,77873,99,441881,87,166384,28,75182,99,566384,43,619.4,0,16:100000:16/64,1537,13,4474,15,1827,18,880,8,7658,22,3864,36
avg:
p34,16G,77567,99,435583,84.6667,163000,27.3333,77724,99,562059,43,613.167,0,16:100000:16/64,1626.67,13.3333,5122,20.3333,1647.33,15,1301.67,12.3333,5789.33,17.6667,3115.67,28.6667
rewrite:
163000 KiB/s
When tarring 4.4GB (of backup files) it takes about 20 seconds on XFS.
Seems to vary as I change my configuration a lot:
Here is from a while back:
Version 1.03 ------Sequential Output------ --Sequential Input-
--Random-
-Per Chr- --Block-- -Rewrite- -Per Chr- --Block--
--Seeks--
Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP
/sec %CP
p34-raid5 15696M 73755 99 411445 75 198639 34 78721 99 483169 39
584.8 0
------Sequential Create------ --------Random
Create--------
p34-raid5,15696M,73755,99,411445,75,198639,34,78721,99,483169,39,584.8,0,16:100000:16/64,919,8,9940,28,2841,18,922,8,3225,10,2422,18
Justin.
next prev parent reply other threads:[~2007-07-14 16:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LRH.0.999.0707131356520.25773@chaos.egr.duke.edu>
2007-07-13 18:35 ` 3ware 9650 tips Justin Piszcz
2007-07-13 18:54 ` Jon Collette
2007-07-13 19:36 ` Justin Piszcz
2007-07-16 2:41 ` David Chinner
2007-07-16 12:22 ` David Chinner
2007-07-16 12:39 ` Bernd Schubert
2007-07-16 15:50 ` Eric Sandeen
2007-07-16 22:21 ` David Chinner
2007-07-16 15:43 ` Joshua Baker-LePain
2007-07-16 17:15 ` [Advocacy] " Bryan J. Smith
2007-07-16 17:40 ` Al Boldi
2007-07-16 17:48 ` Matthew Wilcox
2007-07-16 18:28 ` [RFC] VFS: data=ordered (was: [Advocacy] Re: 3ware 9650 tips) Al Boldi
2007-07-16 19:02 ` Matthew Wilcox
2007-07-16 18:38 ` [Advocacy] Re: 3ware 9650 tips Bryan J. Smith
2007-07-16 17:34 ` Stuart Levy
2007-07-13 19:04 ` Joshua Baker-LePain
2007-07-13 23:30 ` Michael Tokarev
2007-07-14 1:23 ` Andrew Klaassen
2007-07-14 8:08 ` Justin Piszcz
2007-07-14 16:10 ` Andrew Klaassen
2007-07-14 16:11 ` Justin Piszcz
2007-07-14 16:14 ` Andrew Klaassen
2007-07-14 16:18 ` Justin Piszcz [this message]
2007-07-14 9:04 ` Mikael Abrahamsson
2007-07-14 16:11 ` Andrew Klaassen
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.0707141215200.3534@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=clawsoon@yahoo.com \
--cc=jlb17@duke.edu \
--cc=linux-ide-arrays@lists.math.uh.edu \
--cc=linux-raid@vger.kernel.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).