linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Keld Jørn Simonsen" <keld@dkuug.dk>
To: Ben Martin <monkeyiq@users.sourceforge.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: Benchmarks: Linux Kernel RAID vs a Hardware RAID setup
Date: Tue, 15 Jul 2008 18:39:32 +0200	[thread overview]
Message-ID: <20080715163932.GA23164@rap.rap.dk> (raw)
In-Reply-To: <1216130769.5633.318.camel@sam.localdomain>

On Wed, Jul 16, 2008 at 12:06:09AM +1000, Ben Martin wrote:
> Hi,
>   Apologies if posting this here is inappropriate but a recent article
> of mine compares the Linux Kernel RAID code to an $800 hardware RAID
> card and might be of interest to list members:
> 
> http://www.linux.com/feature/140734

It is (at least to me) very interesting to see comparisons on HW vs SW
raid.

I think tho, that you give it some bias not testing the best
configurations for Linux SW raid. For example raid10, the f2 and o2
layouts are faster than n2, and you don't know if Adaptec has some kind
of improved layout.

It would be interesting if you could enhance your article with benchmarks
on raid10, f2 and o2 layouts. I think they would outperform HW raid, at
least on input. And I would like to see how they perform on outout and
rewrite, with ext3 and xfs. We do have some tests, but many of them are
without a file system layer.

I would also welcome test with mobo HW RAID - Many mobo's today come
with some HW raid functionality, and many people would be in the
situation of whether to choose a HW or SW configuration.

best regards
keld

  parent reply	other threads:[~2008-07-15 16:39 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-15 14:06 Benchmarks: Linux Kernel RAID vs a Hardware RAID setup Ben Martin
2008-07-15 14:42 ` Justin Piszcz
2008-07-16  4:14   ` Ben Martin
2008-07-15 15:46 ` Michal Soltys
2008-07-15 20:34   ` Richard Scobie
2008-07-16  2:34     ` Mr. James W. Laferriere
2008-07-16  2:48       ` Richard Scobie
2008-07-16  2:52         ` Mr. James W. Laferriere
2008-07-16  4:17           ` Keld Jørn Simonsen
2008-07-16  5:50       ` Michal Soltys
2008-07-16  3:36   ` Ben Martin
2008-07-16  3:55     ` Richard Scobie
2008-07-16  7:00       ` Dan Williams
2008-07-16 17:08       ` thomas62186218
2008-07-16 19:34         ` Richard Scobie
2008-07-15 16:39 ` Keld Jørn Simonsen [this message]
2008-07-15 16:50   ` thomas62186218
2008-07-15 17:39     ` Keld Jørn Simonsen
2008-07-16  0:01       ` Richard Scobie
2008-07-16  0:20         ` Jon Nelson
2008-07-16  4:06           ` Ben Martin
2008-07-16 15:42           ` Ben Martin
2008-07-16  4:23         ` Keld Jørn Simonsen
2008-07-16  5:18           ` Richard Scobie
2008-07-16  8:17             ` Keld Jørn Simonsen
2008-07-15 17:06   ` Jon Nelson
2008-07-16  3:44     ` Ben Martin
2008-07-15 18:40   ` Brad Campbell
2008-07-15 20:12     ` Keld Jørn Simonsen
2008-07-21 16:55       ` Bill Davidsen
2008-07-23  7:45         ` Keld Jørn Simonsen
2008-07-23 10:29           ` Brad Campbell
     [not found]     ` <487CF499.6080105@harddata.com>
2008-07-15 20:15       ` Keld Jørn Simonsen
2008-07-16  3:58   ` Ben Martin
2008-07-16  4:47     ` Keld Jørn Simonsen
2008-07-21 16:58       ` Bill Davidsen
2008-07-15 19:41 ` Keld Jørn Simonsen
2008-07-16  3:25   ` Ben Martin
2008-07-15 20:40 ` Peter Grandi
2008-07-16  3:38 ` Eric Sandeen
2008-07-16 18:54 ` Alan D. Brunelle
2008-07-17  8:26   ` Ben Martin

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=20080715163932.GA23164@rap.rap.dk \
    --to=keld@dkuug.dk \
    --cc=linux-raid@vger.kernel.org \
    --cc=monkeyiq@users.sourceforge.net \
    /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).