public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* kernbench v0.30
@ 2004-03-01  1:23 Con Kolivas
  2004-03-01 20:57 ` cliff white
  0 siblings, 1 reply; 2+ messages in thread
From: Con Kolivas @ 2004-03-01  1:23 UTC (permalink / raw)
  To: linux kernel mailing list; +Cc: Cliff White

-----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-----

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: kernbench v0.30
  2004-03-01  1:23 kernbench v0.30 Con Kolivas
@ 2004-03-01 20:57 ` cliff white
  0 siblings, 0 replies; 2+ messages in thread
From: cliff white @ 2004-03-01 20:57 UTC (permalink / raw)
  To: Con Kolivas; +Cc: linux-kernel

On Mon, 1 Mar 2004 12:23:25 +1100
Con Kolivas <kernel@kolivas.org> wrote:

> -----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. 
> 

STP version updated also, thanks
cliffw
> 
> 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-----
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


-- 
The church is near, but the road is icy.
The bar is far, but i will walk carefully. - Russian proverb

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2004-03-01 20:58 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-03-01  1:23 kernbench v0.30 Con Kolivas
2004-03-01 20:57 ` cliff white

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox