From: Max Waterman <davidmaxwaterman+gmane@fastmail.co.uk>
To: linux-raid@vger.kernel.org
Subject: Re: md faster than h/w?
Date: Sat, 14 Jan 2006 09:22:16 +0800 [thread overview]
Message-ID: <43C85248.6020405@fastmail.co.uk> (raw)
In-Reply-To: <20060113144640.GA10566@lug.udel.edu>
Ross Vandegrift wrote:
> On Fri, Jan 13, 2006 at 03:06:54PM +0800, Max Waterman wrote:
>> 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.
>
> Sounds like this is probably a bug. If you have some time to play
> around with it, I'd try kernels in between and find out exactly where
> the regression happened. The bug will probably be cleaned up quickly
> and performance will be back where it should be.
>
>> 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?
>
> My employer usues the 1850 more than the 2850, though we do have a few
> in production. My feeling is that 180-200MB/sec is really excellent
> throughput.
>
> We're comparing apples to oranges, but it'll at least give you an
> idea. The Dell 1850s are sortof our highest class of machine that we
> commonly deploy. We have a Supermicro chassis that's exactly like
> the 1850 but SATA instead of SCSI. On the low-end, we have various P4
> Prescott chassis.
>
> Just yesterday I was testing disk performance on a low-end box. SATA
> on a 3Ware controller, RAID1. I was quite pleased to be getting
> 70-80MB/sec.
>
> So my feeling is that your numbers are fairly close to where they
> should be. Faster procs, SCSI, and a better RAID card. However, I'd
> also try RAID1 if you're mostly interested in read speed. Remember
> that RAID1 lets you balance reads across disks, whereas RAID0 will
> require each disk in the array to retrieve the data.
>
OK, this sounds good.
I still wonder where all the theoretical numbers went though.
The scsi channel should be able to handle 320MB/s, and we should have
enough disks to push that (each disk is 147-320MB/s and we have 4 of
them) - theoretically.
Why does the bandwidth seem to plateau with two disks - adding more into
the raid0 doesn't seem to improve performance at all?
Why do I get better numbers using the file for the while device (is
there a better name for it), rather than for a partition (ie /dev/sdb is
faster than /dev/sdb1 - by a lot)?
Can you explain why raid1 would be faster than raid0? I don't see why
that would be...
Things I have to try from your email so far are :
1) raid1 - s/w and h/w (we don't care much about capacity, so it's ok)
2) raid0 - h/w, with bonnie++ using no partition table
3) kernels in between 2.6.8 and 2.6.15
Max.
next prev parent reply other threads:[~2006-01-14 1:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 7:06 md faster than h/w? Max Waterman
2006-01-13 14:46 ` 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 [this message]
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=43C85248.6020405@fastmail.co.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.