From: Stephen Lord <lord@sgi.com>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Alex Davis <alex14641@yahoo.com>,
linux-kernel@vger.kernel.org
Subject: Re: Don't use dbench for benchmarks
Date: Mon, 28 Jan 2002 07:23:11 -0600 [thread overview]
Message-ID: <3C5550BE.6040309@sgi.com> (raw)
In-Reply-To: <E16VBeg-0000YT-00@the-village.bc.nu>
Alan Cox wrote:
>>I must be having a bad day, I can only think of irritable things to post.
>>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.
>>
>
>Im not 100% sure that is the case. Done 30 or 40 times and done from a
>reboot for the 30-40 pass sequence its quite a passable guide to
>both stability and I/O behaviour under some server loads.
>
dbench tells you two things:
o how repeatable your filesystem performance is under load from
multiple processes,
and is the available bandwidth equally shared between the threads.
Various versions
of linux (especially the elevator code) have shown different
characteristics here, but
nowadays things are pretty fair.
o once you have repeatable performance it tells you if your performance
regressed or
improved (on identical hardware of course).
However, there are 'interesting' aspects of the test (and any other
memory stressing
test), it performs better if you push as much out to swap as you can
first. So I find
a dbench 8 runs better after a dbench 64 than it did before it. This
means you need
a VERY controlled environment to make the results mean anything.
Steve
p.s. I really only use it to see if XFS can survive heavy load and
memory pressure.
next prev parent reply other threads:[~2002-01-28 13:24 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 [this message]
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
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=3C5550BE.6040309@sgi.com \
--to=lord@sgi.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox