From: Roger Heflin <rogerheflin@gmail.com>
To: Matt Garman <matthew.garman@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: southbridge/sata controller performance?
Date: Sat, 03 Jan 2009 14:11:38 -0600 [thread overview]
Message-ID: <495FC67A.2030201@gmail.com> (raw)
In-Reply-To: <20090103193429.GA17462@sewage.raw-sewage.fake>
Matt Garman wrote:
> When using Linux software RAID, I was thinking that, from a
> performance perspective, the southbridge/SATA controller is probably
> one of the most important components (assuming a reasonable CPU).
> Is this a correct generalization?
>
> If it is, has anyone done a study or benchmarked SATA controller
> performance? Particularly with consumer-grade hardware?
>
> I haven't been able to find much info about this on the web; the
> Tech Report seems to consistently benchmark SATA performance:
>
> AMD SB600: http://techreport.com/articles.x/13832/5
> AMD SB700: http://techreport.com/articles.x/14261/10
> AMD SB750: http://techreport.com/articles.x/13628/9
> Intel ICH10: http://techreport.com/articles.x/15653/9
> nVidia GeForce 8300: http://techreport.com/articles.x/14993/9
In general those benchmarks are mostly useless for Raid.
The biggest different for RAID is what happens when multiple channels
are used. On full speed streaming read/write almost every (even the
worst PCI controllers on a PCI bus) sata controller is close to equal
when you only have one drive, once you use 2 drives or more things
change. If the given controller setup can actually run several
drives at close to full single drive speed performance will be good,
if it cannot things are going to get much slower.
One test I do is a single dd from one disk and watch the io speed, and
then I add dd's and watch what happens. I have 4 identical disks, 2
are on a ICH7, 2 are on a pci bus based MB controller, any single of
these disks will do about 75MB/second no matter were it is, using 2 on
the ich7 gets about 140-150MB/second, using the 2 on the pci bus based
MB controller gets 98MB/second. If all of the controllers
techreports tested were equal on this test, then it might be worth it
to look at the benchmarks techreport is using, but the simple dd
benchmark is likely more important, and I am pretty sure that someone
could use a controller (on a bandwidth limited bus) that would do good
on the above techreport benchmark, but fail horribly when several
disks with a high io speed were being used and work badly for raid.
next prev parent reply other threads:[~2009-01-03 20:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-03 19:34 southbridge/sata controller performance? Matt Garman
2009-01-03 20:11 ` Roger Heflin [this message]
2009-01-04 9:55 ` Justin Piszcz
2009-01-04 19:40 ` Matt Garman
2009-01-04 21:02 ` Roger Heflin
2009-01-04 21:34 ` Justin Piszcz
2009-01-05 3:27 ` Matt Garman
2009-01-05 7:08 ` Keld Jørn Simonsen
2009-01-05 14:21 ` Matt Garman
2009-01-05 16:11 ` Keld J?rn Simonsen
2009-01-13 20:28 ` Matt Garman
2009-01-14 22:34 ` Bill Davidsen
2009-01-04 21:32 ` Justin Piszcz
2009-01-05 0:27 ` Keld Jørn Simonsen
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=495FC67A.2030201@gmail.com \
--to=rogerheflin@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=matthew.garman@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).