From: Max Waterman <davidmaxwaterman+gmane@fastmail.co.uk>
To: Ross Vandegrift <ross@lug.udel.edu>
Cc: linux-raid@vger.kernel.org
Subject: Re: md faster than h/w?
Date: Mon, 16 Jan 2006 12:37:40 +0800 [thread overview]
Message-ID: <43CB2314.5000203@fastmail.co.uk> (raw)
In-Reply-To: <20060114212341.GB20464@lug.udel.edu>
Ross Vandegrift wrote:
> On Sat, Jan 14, 2006 at 01:40:53AM -0500, Mark Hahn wrote:
>>> 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.
>> there are some funny interactions between partitions, filesystems
>> and low-level parameters like readahead.
>
> Hmmm, I'm not convinced, though it could be that the disks in my
> workstation are not fast enough.
>
> I used hdparm and your iorate program to compare the performance on my
> fastest disk (7200rpm, ATA100). The difference between partition vs.
> disk is definitely within the margin of error: 2-3MB/sec when I'm
> averaging around 50MB/sec.
>
> I'd be suspicious of much more difference between the two...
In which case, I'm suspicious - using 'hdparm -t' on h/w RAID0 (4 disks) :
/dev/sdb:
Timing buffered disk reads: 536 MB in 3.00 seconds = 178.57 MB/sec
/dev/sdb1:
Timing buffered disk reads: 100 MB in 3.01 seconds = 33.19 MB/sec
That's a big difference in my book.
However, with bonnie++, using filesystems created on the above devices,
I get similar numbers :
/dev/sdb:
--Sequential Input--
-Per Chr- --Block--
K/sec %CP K/sec %CP
38586 76 126818 15
/dev/sdb1:
--Sequential Input-
-Per Chr- --Block--
K/sec %CP K/sec %CP
38185 76 127569 15
After running that, I reran hdparm, and it reported ~40MB for *both*
/dev/sdb and /dev/sdb1.
Then I unmount /dev/sdb and it's back up to 155MB/s !?!?!
It's not making any sense to me :(
Strange. I guess I should just ignore 'hdparm -t'?
Max.
next prev parent reply other threads:[~2006-01-16 4:37 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
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 [this message]
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=43CB2314.5000203@fastmail.co.uk \
--to=davidmaxwaterman+gmane@fastmail.co.uk \
--cc=linux-raid@vger.kernel.org \
--cc=ross@lug.udel.edu \
/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).