From: Con Kolivas <kernel@kolivas.org>
To: linux kernel mailing list <linux-kernel@vger.kernel.org>
Cc: Cliff White <cliffw@osdl.org>
Subject: kernbench v0.30
Date: Mon, 1 Mar 2004 12:23:25 +1100 [thread overview]
Message-ID: <200403011223.31059.kernel@kolivas.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Kernbench v0.30
http://ck.kolivas.org/kernbench/
Changelog:
v0.30 Added fast run option which bypasses caching, warmup and tree
preparation and drops number of runs to 3. Modified half loads to
detect -j2 and change to -j3. Added syncs. Improved warnings and
messages.
What is this?
This is a cpu throughput benchmark originally devised and used by Martin J.
Bligh. It is designed to compare kernels on the same machine, or to compare
hardware. To compare hardware you need to be running the same architecture
machines (eg i386) and run kernbench on the same kernel source tree.
It runs a kernel at various numbers of concurrent jobs: 1/2 number of cpus,
optimal (default is 4xnumber of cpus) and maximal job count. Optionally it can
also run single threaded. It then prints out a number of useful statistics
for the average of each group of runs.
You need at least 2Gb of ram for this to be a true throughput benchmark or
else you will get swapstorms.
Ideally it should be run in single user mode on a non-journalled filesystem.
To compare results it should always be run in the same kernel tree.
How do I use it?
You need a kernel tree (any will do) and the applications 'time' and 'awk'
installed. 'time' is different to the builtin time used by BASH and has more
features desired for this benchmark.
Simply cd into the kernel tree directory and type
/path/to/kernbench
Options
kernbench [-n runs] [-o jobs] [-s] [-H] [-O] [-M] [-h] [-v]
n : number of times to perform benchmark (default 5)
o : number of jobs for optimal run (default 4 * cpu)
s : perform single threaded runs (default don't)
H : don't perform half load runs (default do)
O : don't perform optimal load runs (default do)
M : don't perform maximal load runs (default do)
f : fast run
h : print this help
v : print version number
Con
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQFAQpCPZUg7+tp6mRURAgvfAJ4lyrnuOns0NSvCY9usWnnhiv2ZpQCbBI04
zvd+1jYdtTwFatWBUEuoERI=
=Eq2l
-----END PGP SIGNATURE-----
next reply other threads:[~2004-03-01 1:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 1:23 Con Kolivas [this message]
2004-03-01 20:57 ` kernbench v0.30 cliff white
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=200403011223.31059.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=cliffw@osdl.org \
--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