From: Andrew Morton <akpm@zip.com.au>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: Alex Davis <alex14641@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: Don't use dbench for benchmarks
Date: Mon, 28 Jan 2002 11:02:00 -0800 [thread overview]
Message-ID: <3C55A028.3FD71164@zip.com.au> (raw)
In-Reply-To: <20020128144319.67654.qmail@web9203.mail.yahoo.com>, <20020128144319.67654.qmail@web9203.mail.yahoo.com> <E16VGmX-0000BQ-00@starship.berlin>
Daniel Phillips wrote:
>
> On January 28, 2002 03:43 pm, Alex Davis wrote:
> > > Continuing that theme: please don't use dbench for benchmarks. At all.
> > > It's an unreliable indicator of anything in particular except perhaps
> > > stability. Please, use something else for your benchmarks.
> >
> > What do you suggest as an acceptable benchmark???
>
> A benchmark that tests disk/file system create/read/write/delete throughput,
> as dbench is supposed to? Though I haven't used it personally, others
> (Arjan) have suggested tiobench:
>
> http://tiobench.sourceforge.net/
>
Also http://www.iozone.org/
Really, iozone isn't a benchmark as much as the "engine" of
a benchmark. It has so many options that you can use it
to build higher-level, more intelligent test suites by invoking it
in specific ways. read/write, mmap, MS_SYNC, MS_ASYNC, O_DIRECT,
aio, O_SYNC, fsync(), multiple threads, ...
-
prev parent reply other threads:[~2002-01-28 19:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-27 4:35 some rmap12a benchmarks Alex Davis
2002-01-28 11:56 ` Don't use dbench for benchmarks Daniel Phillips
2002-01-28 13:17 ` Alan Cox
2002-01-28 13:23 ` Stephen Lord
2002-01-28 14:43 ` Alex Davis
2002-01-28 15:32 ` Richard B. Johnson
2002-01-28 16:56 ` Nigel Gamble
2002-01-28 17:55 ` Richard B. Johnson
2002-01-28 20:28 ` Nigel Gamble
2002-01-28 18:45 ` Daniel Phillips
2002-01-28 19:02 ` Andrew Morton [this message]
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=3C55A028.3FD71164@zip.com.au \
--to=akpm@zip.com.au \
--cc=alex14641@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.