Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Ben Martin <monkeyiq@users.sourceforge.net>
To: Jon Nelson <jnelson-linux-raid@jamponi.net>
Cc: "Richard Scobie" <richard@sauce.co.nz>,
	"Keld Jørn Simonsen" <keld@dkuug.dk>,
	thomas62186218@aol.com, 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 14:06:59 +1000	[thread overview]
Message-ID: <1216181219.5633.372.camel@sam.localdomain> (raw)
In-Reply-To: <cccedfc60807151720x62cdbb3cx2c772ac884f97fde@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2430 bytes --]

On Tue, 2008-07-15 at 19:20 -0500, Jon Nelson wrote:
> On Tue, Jul 15, 2008 at 7:01 PM, Richard Scobie <richard@sauce.co.nz> wrote:
> > Keld Jørn Simonsen wrote:
> >
> >> I would actually welcome more tests with specific user profiles, like
> >> many small reads and writes for database  use, and concurrent random
> >> reading and writing to simulate the load on a server. What bonnie++ is
> >> reporting is only equential IO. This is important on work stations, but
> >> actually not on servers.
> >
> > The following is from the Bonnie++ man page:
> >
> > "There  are  two  sections  to the program's operations. The first is to
> > test the IO throughput in a fashion that is designed to  simulate  some
> > types of database applications. The second is to test creation, reading and
> > deleting many small files in a fashion similar to the usage patterns of
> > programs such as Squid or INN."
> >
> > So I guess the author thinks it's valid for more than sequential I/O.
> >
> > In any case, while we may be in a minority, Justin, I and a few others are
> > interested in sequential I/O, as we build servers required to read
> and write
> > multiple streams of uncompressed SD and HD video in realtime.
> 
> In that case, the 'fstest' program (google for it, it's associated
> with the samba folks IIRC), might be just the ticket.
> You specify the number of children (real children, not threads), the
> number of files each child will open, populate, verify, and then
> delete, the size of the files, and a few other options. It very nicely
> simulates a set of totally greedy I/O intensive processes.
> 

I was thinking of benchmarks at a higher level too. 

fstest and fio seem like good candidates for making a configuration that
tests performance that can be easily run on another system without much
setup required.

A few other ideas I had were using postal for simulating a mail server
env and doing "something" with PostgreSQL. The latter is really a fairly
large can of worms because you would need to lock down the various RAID
caches, read aheads (which might actually adversely effect performance
if the kernel second guesses PG badly), the pg configuration (eg, its
caching settings) and of course where the base tables and indexes landed
on disk.

If anyone has pointers for testing PG performance on RAID I'd love to
hear about them either on / off list.


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-07-16  4:06 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 [this message]
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=1216181219.5633.372.camel@sam.localdomain \
    --to=monkeyiq@users.sourceforge.net \
    --cc=jnelson-linux-raid@jamponi.net \
    --cc=keld@dkuug.dk \
    --cc=linux-raid@vger.kernel.org \
    --cc=richard@sauce.co.nz \
    --cc=thomas62186218@aol.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