From: Ben Martin <monkeyiq@users.sourceforge.net>
To: Jon Nelson <jnelson-linux-raid@jamponi.net>
Cc: "Keld Jørn Simonsen" <keld@dkuug.dk>,
linux-raid@vger.kernel.org,
"Ben Martin" <monkeyiq@users.sourceforge.net>
Subject: Re: Benchmarks: Linux Kernel RAID vs a Hardware RAID setup
Date: Wed, 16 Jul 2008 13:44:46 +1000 [thread overview]
Message-ID: <1216179886.5633.353.camel@sam.localdomain> (raw)
In-Reply-To: <cccedfc60807151006mbcf58e2udd725f3b7bd38637@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 996 bytes --]
This sounds perfect for an article that compares mobo fakeraid/bois-raid
for RAID-10 (if a board with it can be decided on) and kernel RAID-10. A
line graph of the bonnie xfer stats from say 16kb chunks through 1mb.
If/when I get this happening I'll post a link again to the list.
On Tue, 2008-07-15 at 12:06 -0500, Jon Nelson wrote:
> I would add to that request that you consider using a smaller chunk size.
> My own benchmarks showed that for some raid levels and layouts, a
> smaller chunk size gave the best overall performance.
>
>
> On Tue, Jul 15, 2008 at 11:39 AM, Keld Jørn Simonsen <keld@dkuug.dk> wrote:
> ...
> > 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.
>
>
>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-07-16 3:44 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
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 [this message]
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=1216179886.5633.353.camel@sam.localdomain \
--to=monkeyiq@users.sourceforge.net \
--cc=jnelson-linux-raid@jamponi.net \
--cc=keld@dkuug.dk \
--cc=linux-raid@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox