From: Max Waterman <davidmaxwaterman+gmane@fastmail.co.uk>
To: linux-raid@vger.kernel.org
Subject: md faster than h/w?
Date: Fri, 13 Jan 2006 15:06:54 +0800 [thread overview]
Message-ID: <dq7jii$n1c$1@sea.gmane.org> (raw)
Hi,
I've been trying to increase the i/o performance of a new server.
The server is a Dell PowerEdge 2850. It has 2(x2) Intel Xeon 3GHz CPUs,
4GB RAM, a Perc4/DC RAID controller (AKA MegaRAID SCSI 320-2), and we
have 5 Fujitsu MAX3073NC drives attached to one of it's channels (can't
use the other channel due to a missing 'option').
According to Fujitsu's web site, the disks can each do internal IO at
upto 147MB/s, and burst upto 320MB/s. According to the LSI Logic web
page, the controller can do upto 320MB/s. All theoretical numbers, of
course.
So, we're trying to measure the performance. We've been using 'bonnie++'
and 'hdparm -t'.
We're primarily focusing on read performance at the moment.
We set up the os (debian) on one of the disks (sda), and we're playing
around with the others in various configurations.
I figured it'd be good to measure the maximum performance of the array,
so we have been working with the 4 disks in a raid0 configuration
(/dev/sdb).
Initially, we were getting 'hdparm -t' numbers around 80MB/s, but this
was when we were testing /dev/sdb1 - the (only) partition on the device.
When we started testing /dev/sdb, it increased significantly to around
180MB/s. I'm not sure what to conclude from this.
In any case, our bonnie++ results weren't so high, at around 100MB/s.
Using theoretical numbers as a maximum, we should be able to read at the
greater of 4 times a single drive speed (=588MB/s) or the SCSI bus speed
(320MB/s) ie 320MB/s.
So, 100MB/s seems like a poor result.
I thought I'd try one other thing and that was to configure the drives
as JBOD (which is actually having each one as RAID0 in the controller
config s/w), and configure as s/w raid0.
Doing this initially resulted in a doubling of bonnie++ speed at over
200MB/s, though I have been unable to reproduce this result - the most
common result is still about 180MB/s.
One further strangeness is that our best results have been while using a
uni-processor kernel - 2.6.8. We would prefer it if our best results
were with the most recent kernel we have, which is 2.6.15, but no.
So, any advice on how to obtain best performance (mainly web and mail
server stuff)?
Is 180MB/s-200MB/s a reasonable number for this h/w?
What numbers do other people see on their raid0 h/w?
Any other advice/comments?
Max.
next reply other threads:[~2006-01-13 7:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 7:06 Max Waterman [this message]
2006-01-13 14:46 ` md faster than h/w? Ross Vandegrift
2006-01-13 21:08 ` Lajber Zoltan
2006-01-14 1:19 ` Max Waterman
2006-01-14 2:05 ` Ross Vandegrift
2006-01-14 8:26 ` Max Waterman
2006-01-14 10:42 ` Michael Tokarev
2006-01-14 11:48 ` Max Waterman
2006-01-14 18:14 ` Mark Hahn
2006-01-14 1:22 ` Max Waterman
2006-01-14 6:40 ` Mark Hahn
2006-01-14 8:54 ` Max Waterman
2006-01-14 21:23 ` Ross Vandegrift
2006-01-16 4:37 ` Max Waterman
2006-01-16 5:33 ` Max Waterman
2006-01-16 14:12 ` Andargor
2006-01-17 9:18 ` Max Waterman
2006-01-17 17:09 ` Andargor
2006-01-18 4:43 ` Max Waterman
2006-01-16 6:31 ` Max Waterman
2006-01-16 13:30 ` Ric Wheeler
2006-01-16 14:08 ` Mark Hahn
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='dq7jii$n1c$1@sea.gmane.org' \
--to=davidmaxwaterman+gmane@fastmail.co.uk \
--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).