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: Tue, 25 Sep 2007 19:25:35 +0200 [thread overview]
Message-ID: <20070925172535.GD20499@p15145560.pureserver.info> (raw)
In-Reply-To: <152219.84729.qm@web32906.mail.mud.yahoo.com>
Bryan J. Smith schrieb:
> Ralf Gross <Ralf-Lists@ralfgross.de> wrote:
> ...
> I'm completely biased though, I assemble file and database servers,
> not web or other CPU-bound systems. Turning my system interconnect
> (not the CPU, a PC CPU crunches XOR very fast) into a bottlenecked
> PIO operation is not ideal for NFS writes or large record SQL commits
> in my experience. Heck, one look at NetApp's volume w/NVRAM and
> SPE-accelerated RAID-4 designs will quickly change your opinion as
> well (and make you wonder if they aren't worth the cost at times as
> well ;).
Thanks for all the details. Before I leave the office (it's getting
dark here): I think the Overland RAID we have (48x Disk) is from the
same manufacturer (Xyratex) that builds some devices for NetApp.
Our profile is not that performance driven, thus the ~200MB/s
read/write performace is ok. We just need cheap storage ;)
Still I'm wondering how other people saturate a 4 Gb FC controller
with one single RAID 5. At least that's what I've seen in some
benchmarks and here on the list.
If dd doesn't give me more than 200MB/s, the problem could only be the
array, the controller or the FC connection. Given that other setup are
similar and not using different controllers and stripes.
Ralf
next prev parent reply other threads:[~2007-09-25 17:26 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
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 [this message]
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=20070925172535.GD20499@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