From: Daniel Phillips <phillips@innominate.de>
To: linux-kernel@vger.kernel.org
Subject: File I/O benchmarks for various kernel
Date: Fri, 29 Dec 2000 23:56:30 +0100 [thread overview]
Message-ID: <3A4D169E.B60B356F@innominate.de> (raw)
I've been using dbench a lot lately for reality checks on various kernel
mods, and out of interest I decided to run benchmarks with it on a few
different kernel versions. I noticed a major difference between 2.2 and
2.4 kernels - 2.4 is running the benchmarks about 3 times faster than
2.2, and it seems to be getting faster with each step towards 2.4.0. On
the other hand, 2.2 seems to be getting slower. Here are a few points
on the curve.
Test machine: 64 meg, 500 Mhz K6, IDE, Ext2, Blocksize=4K
Test: dbench 48
Kernel Throughput Elapsed Time
------ ---------- ------------
2.2.16 3.1 MB/sec 33 min 53 secs
2.2.18 2.8 MB/sec 38 min 10 secs
2.2.19-pre3 2.7 MB/sec 39 min 44 secs
2.4.0-test12 7.3 MB/sec 14 min 32 secs
2.4.0-test13-pre4 9.5 MB/sec 11 min 06 secs
2.4.0-test13-pre5 10.8 MB/sec 9 min 48 secs
Dbench was written by Andrew Tridgell to measure disk performance under
simulated samba network traffic load. The '48' means it's simulating
the file access patterns of 48 network clients, all doing heavy io at
the same time.
For anyone interested in checking these results on their own hardware,
dbench is available at:
ftp://samba.org/pub/tridge/dbench/dbench-1.1.tar.gz
--
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-12-29 23:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-29 22:56 Daniel Phillips [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-12-30 17:03 File I/O benchmarks for various kernel Ed Tomlinson
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=3A4D169E.B60B356F@innominate.de \
--to=phillips@innominate.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox