From: "E. Gryaznova" <grev@namesys.com>
To: linux-kernel@vger.kernel.org
Subject: Can dbench be used for benchmarking fs?
Date: Tue, 07 Oct 2003 16:42:46 +0400 [thread overview]
Message-ID: <3F82B4C6.707221A@namesys.com> (raw)
Hello.
I use dbench for benchmarking the file systems and some results are
suspicious for me.
I run 10 times dbench on ext3 and i have the following :
Throughput 16.6754 MB/sec (NB=20.8443 MB/sec 166.754 MBit/sec)
Throughput 22.9772 MB/sec (NB=28.7216 MB/sec 229.772 MBit/sec)
Throughput 22.3698 MB/sec (NB=27.9623 MB/sec 223.698 MBit/sec)
Throughput 19.0533 MB/sec (NB=23.8167 MB/sec 190.533 MBit/sec)
Throughput 21.9662 MB/sec (NB=27.4577 MB/sec 219.662 MBit/sec)
Throughput 23.4062 MB/sec (NB=29.2578 MB/sec 234.062 MBit/sec)
Throughput 21.4233 MB/sec (NB=26.7791 MB/sec 214.233 MBit/sec)
Throughput 20.6202 MB/sec (NB=25.7753 MB/sec 206.202 MBit/sec)
Throughput 15.7005 MB/sec (NB=19.6256 MB/sec 157.005 MBit/sec)
Throughput 19.9631 MB/sec (NB=24.9538 MB/sec 199.631 MBit/sec)
As you can see
the average Throughput value is equal 20.4155 MB/sec
the max value 23.4062 MB/sec and
the min value 15.7005 MB/sec
As the result: the measuring deviation is equal = 23.4062 - 15.7005 =
7.7057 or about ~38% from average value.
I have dbench-1.1.tar.gz
I run dbench by the following way :
mke2fs -j /dev/xxx
mount /dev/xxx /mnt
cp dbench /mnt/.
cp clients.txt /mnt/.
cd /mnt
for x 1, 2, ... 10
do
./dbench 8 >>results
done
So, I have 2 questions :
1. Is there a way to avoid such big deviations on measuring a file
systems throughput and to get more stable results?
2. Can dbench be used for benchmarking the file systems and if it is so
-- what is the predictable error on the measuring?
Thank you very much for helping.
Lena.
next reply other threads:[~2003-10-07 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 12:42 E. Gryaznova [this message]
2003-10-07 14:29 ` Can dbench be used for benchmarking fs? Andreas Dilger
2003-10-07 14:45 ` Nikita Danilov
2003-10-07 15:59 ` Andreas Dilger
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=3F82B4C6.707221A@namesys.com \
--to=grev@namesys.com \
--cc=linux-kernel@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 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.