From: Ralf Gross <Ralf-Lists@ralfgross.de>
To: linux-xfs@oss.sgi.com
Subject: Re: mkfs options for a 16x hw raid5 and xfs (mostly large files)
Date: Mon, 24 Sep 2007 23:52:23 +0200 [thread overview]
Message-ID: <20070924215223.GC4082@p15145560.pureserver.info> (raw)
In-Reply-To: <Pine.LNX.4.64.0709241736370.19847@p34.internal.lan>
Justin Piszcz schrieb:
> >>I find that to be the case with SW RAID (defaults are best)
> >>
> >>Although with 16 drives(?) that is awfully slow.
> >>
> >>I have 6 SATA's I get 160-180 MiB/s raid5 and 250-280 MiB/s raid 0 (sw
> >>raid).
> >>
> >>With 10 raptors I get ~450 MiB/s write and ~550-600 MiB/s read, again
> >>XFS+SW raid.
> >
> >Hm, with the different HW-RAIDs I've used so far (easyRAID,
> >Infortrend, internal Areca controller), I always got 160-200 MiB/s
> >read/write with 7-15 disks. That's one reason why I asked if there are
> >some xfs options I could use for better performance. But I guess fs
> >options won't boost performance that much.
>
> What do you get when (reading) from the raw device?
>
> dd if=/dev/sda bs=1M count=10240
The server has 16 GB RAM, so I tried it with 20 GB of data.
dd if=/dev/sdd of=/dev/null bs=1M count=20480
20480+0 Datensätze ein
20480+0 Datensätze aus
21474836480 Bytes (21 GB) kopiert, 95,3738 Sekunden, 225 MB/s
and a second try:
dd if=/dev/sdd of=/dev/null bs=1M count=20480
20480+0 Datensätze ein
20480+0 Datensätze aus
21474836480 Bytes (21 GB) kopiert, 123,78 Sekunden, 173 MB/s
I'm taoo tired to interprete these numbers at the moment, I'll do some
more testing tomorrow.
Good night,
Ralf
next prev parent reply other threads:[~2007-09-24 21:52 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-23 9:38 mkfs options for a 16x hw raid5 and xfs (mostly large files) Ralf Gross
2007-09-23 12:56 ` Peter Grandi
2007-09-26 14:54 ` Ralf Gross
2007-09-26 16:27 ` [UNSURE] " Justin Piszcz
2007-09-26 16:54 ` Ralf Gross
2007-09-26 16:59 ` Justin Piszcz
2007-09-26 17:38 ` Bryan J. Smith
2007-09-26 17:41 ` Justin Piszcz
2007-09-26 17:55 ` Bryan J. Smith
2007-09-26 17:13 ` [UNSURE] " Bryan J. Smith
2007-09-26 17:27 ` Justin Piszcz
2007-09-26 17:35 ` Bryan J. Smith
2007-09-26 17:37 ` Justin Piszcz
2007-09-26 17:38 ` Justin Piszcz
2007-09-26 17:49 ` Bryan J. Smith
2007-09-27 15:22 ` Ralf Gross
2007-09-24 17:31 ` Ralf Gross
2007-09-24 18:01 ` Justin Piszcz
2007-09-24 20:39 ` Ralf Gross
2007-09-24 20:43 ` Justin Piszcz
2007-09-24 21:33 ` Ralf Gross
2007-09-24 21:36 ` Justin Piszcz
2007-09-24 21:52 ` Ralf Gross [this message]
2007-09-25 12:35 ` Ralf Gross
2007-09-25 12:50 ` Justin Piszcz
2007-09-25 13:44 ` Bryan J Smith
2007-09-25 12:57 ` KELEMEN Peter
2007-09-25 13:49 ` Ralf Gross
2007-09-25 14:08 ` Bryan J Smith
2007-09-25 16:07 ` Ralf Gross
2007-09-25 16:28 ` Bryan J. Smith
2007-09-25 17:25 ` Ralf Gross
2007-09-25 17:41 ` Bryan J. Smith
2007-09-25 19:13 ` Ralf Gross
2007-09-25 20:23 ` Bryan J. Smith
2007-09-25 16:48 ` Justin Piszcz
2007-09-25 18:00 ` Bryan J. Smith
2007-09-25 18:33 ` Ralf Gross
2007-09-25 23:38 ` Justin Piszcz
2007-09-26 8:23 ` Ralf Gross
2007-09-26 8:42 ` Justin Piszcz
2007-09-26 8:49 ` Ralf Gross
2007-09-26 9:52 ` Justin Piszcz
2007-09-26 15:03 ` Bryan J Smith
2007-09-26 15:15 ` Ralf Gross
2007-09-26 17:08 ` Bryan J. Smith
2007-09-26 16:24 ` Justin Piszcz
2007-09-26 17:11 ` Bryan J. Smith
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=20070924215223.GC4082@p15145560.pureserver.info \
--to=ralf-lists@ralfgross.de \
--cc=linux-xfs@oss.sgi.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