From: Ed Sweetman <safemode@comcast.net>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: poor raid0 performance in 2.6.16-rc1-mm2?
Date: Tue, 24 Jan 2006 19:19:49 -0500 [thread overview]
Message-ID: <43D6C425.90901@comcast.net> (raw)
In-Reply-To: <20060125011211.337169ac@werewolf.auna.net>
J.A. Magallon wrote:
>On Tue, 24 Jan 2006 18:27:53 -0500, Ed Sweetman <safemode@comcast.net> wrote:
>
>
>
>>I'll have to reboot to double check that this is specific to the above
>>kernel version, but It seems something is either wrong with my
>>particular kernel config for raid0, or my raid0 is setup wrong.
>>
>>my raid0 uses 64k chunk sizes on an ext3 fs that's 367GB large, (across
>>two identical sata disks on nforce4 chipset)
>>
>>I have partitions on both drives of equal size (2 altogether) that are
>>outside of the raid0. I dbenched those partitions, the raid0 device,
>>and libata pata devices i also have (same rpm, less cache, same company).
>>
>>pata disk : 403MB/sec
>>sata disk 1: 446MB/sec
>>raid0 : between 336MB/sec and 386MB/sec
>>
>>
>>
>
>Uh ? I want some of those disks....
>How are you measuring that ?
>
>Some more real numbers.
>
>A SATA raid5:
>nada:~# lsscsi
>[1:0:0:0] disk ATA Maxtor 7Y250M0 YAR5 -
>[2:0:0:0] disk ATA Maxtor 7Y250M0 YAR5 -
>[3:0:0:0] disk ATA Maxtor 7Y250M0 YAR5 -
>[4:0:0:0] disk ATA Maxtor 7Y250M0 YAR5 -
>[5:0:0:0] disk ATA Maxtor 7Y250M0 YAR5 -
>[6:0:0:0] disk ATA Maxtor 7Y250M0 YAR5 -
>[7:0:0:0] disk ATA Maxtor 7Y250M0 YAR5 -
>nada:~# hdparm -t /dev/sdb /dev/sdc
>
>/dev/sdb:
> Timing buffered disk reads: 156 MB in 3.02 seconds = 51.70 MB/sec
>
>/dev/sdc:
> Timing buffered disk reads: 154 MB in 3.02 seconds = 50.96 MB/sec
>
>nada:~# hdparm -t /dev/md0
>
>/dev/md0:
> Timing buffered disk reads: 148 MB in 3.01 seconds = 49.20 MB/sec
>
>An SCSI raid0 one (160 and 320 mixed...)
>
>annwn:~# hdparm -t /dev/sdc /dev/sdb
>
>/dev/sdc:
> Timing buffered disk reads: 226 MB in 3.02 seconds = 74.72 MB/sec
>
>/dev/sdb:
> Timing buffered disk reads: 122 MB in 3.00 seconds = 40.64 MB/sec
>
>annwn:~# hdparm -t /dev/md0
>
>/dev/md0:
> Timing buffered disk reads: 242 MB in 3.00 seconds = 80.62 MB/sec
>
>
I was using dbench with three threads. In retrospect, I am pretty sure
my 2GB of ram was creating that performance. Though, the poor
performance when run on the raid0 device still stands.
This performance hit doesn't exist when using hdparm to test the
bandwidth of the devices
/dev/sdc:
Timing buffered disk reads: 166 MB in 3.01 seconds = 55.19 MB/sec
psuedomode:/mnt# hdparm -t /dev/sda
/dev/sda:
Timing buffered disk reads: 126 MB in 3.02 seconds = 41.72 MB/sec
psuedomode:/mnt# hdparm -t /dev/md0
/dev/md0:
Timing buffered disk reads: 338 MB in 3.02 seconds = 112.07 MB/sec
sda is pata libata
sdc is sata libata
md0 is two identical sata libata devices (sdc and sdd) in RAID0
So apparently, this may be filesystem related, as it pertains to being
in a raid setup (since the filesystems are all the same otherwise except
size).
>
>
>>now the sata disks alone, get 446MB/sec, but the raid device that's
>>comprised of them is getting >60MB/sec less throughput.
>>
>>This difference is much more drastic when say only 1 process is used
>>with dbench,
>>
>>sata disk 1: 230MB/sec
>>raid0 : 96MB/sec
>>
>>
>>Something definitely feels wrong with these numbers.
>>
>>All filesystems are ext3, on an athlon 64 x2 system, during each test no
>>other io was performed, there is no swap and no other cpu intensive
>>operations were going on.
>>
>>the filesystems were all created the same way, and all have the same
>>blocksizes and such. All are mounted with default options too.
>>-
>>
>>
next prev parent reply other threads:[~2006-01-25 0:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 23:27 poor raid0 performance in 2.6.16-rc1-mm2? Ed Sweetman
2006-01-25 0:12 ` J.A. Magallon
2006-01-25 0:19 ` Ed Sweetman [this message]
2006-01-25 2:19 ` Grant Coady
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=43D6C425.90901@comcast.net \
--to=safemode@comcast.net \
--cc=jamagallon@able.es \
--cc=linux-kernel@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.