From: Jesper Juhl <jesper.juhl@gmail.com>
To: eliad lubovsky <eliadl@013.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux Benchmarks
Date: Wed, 20 Jul 2005 16:36:25 +0200 [thread overview]
Message-ID: <9a874849050720073665b87c50@mail.gmail.com> (raw)
In-Reply-To: <9a87484905072007075a9b0bba@mail.gmail.com>
On 7/20/05, Jesper Juhl <jesper.juhl@gmail.com> wrote:
> On 7/20/05, eliad lubovsky <eliadl@013.net> wrote:
> > Where can I find common Linux benchmarks? I added some changes to system
> > calls and want to check whether it cause any performance degradation.
> > Thanks,
> >
> You could go search Google - http://google.com/
> You could go search Freshmeat - http://freshmeat.net/
> You could go search almost any Linux software archive...
>
> Luckily for you I'm a bit bored and have 2min to spare, so I'll list a
> few for you, but in the future, please try finding them yourself
> first...
>
> aiostress
> ftp://ftp.suse.com/pub/people/mason/utils/aio-stress.c
>
> bonnie
> http://www.garloff.de/kurt/linux/bonnie/
>
> clyde
> http://tdec.free.fr/clyde/clyde.en.html
>
> contest
> http://contest.kolivas.org/
>
> dbench
> http://samba.org/ftp/tridge/dbench/
>
> interbench
> http://interbench.kolivas.org/
>
> iozone
> http://www.iozone.org/
>
> lmbench
> http://www.bitmover.com/lmbench/
>
> nbench
> http://www.tux.org/~mayer/linux/bmark.html
>
> netperf
> http://www.netperf.org/
>
> re-aim
> http://sourceforge.net/projects/re-aim-7
>
> sysbench
> http://sysbench.sourceforge.net/
>
> tbench
> http://gnunet.org/doxygen/html/dir_000026.html
>
> volanomark
> http://www.volano.com/benchmarks.html
>
>
For the bennefit of people searching the archives, I guss I might as
well list a few more now that I'm at it :
bonnie++
http://www.coker.com.au/bonnie%2B%2B/
cpuburn
http://pages.sbcglobal.net/redelm/
glxgears
http://www.xfree86.org/4.4.0/glxgears.1.html
hdparm (hdparm -tT /dev/drive_to_test)
http://sourceforge.net/projects/hdparm/
http://www.die.net/doc/linux/man/man8/hdparm.8.html
iometer
http://www.iometer.org/
jmeter
http://jakarta.apache.org/jmeter/index.html
kernprof
http://oss.sgi.com/projects/kernprof/
llcbench
http://icl.cs.utk.edu/projects/llcbench/index.html
lockmeter
http://oss.sgi.com/projects/lockmeter/
openssl (openssl -speed)
http://www.openssl.org/docs/apps/speed.html
siege
http://www.joedog.org/siege/
spec
http://www.spec.org/
specviewperf
http://www.spec.org/gpc/opc.static/viewperf71info.html
stream
http://www.cs.virginia.edu/stream/
stress
http://weather.ou.edu/~apw/projects/stress/
testvidinfo (test program part of the SDL library source, contains a
-benchmark mode)
http://www.libsdl.org/
vmregress
http://www.skynet.ie/~mel/projects/vmregress/
And while not really a benchmark tool, the Linux Test Project's test
suite may also be good to use to test for regressions :
http://ltp.sourceforge.net/
StressLinux (http://www.stresslinux.org/) may also be of interrest.
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
prev parent reply other threads:[~2005-07-20 14:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-20 13:42 Linux Benchmarks eliad lubovsky
2005-07-20 14:07 ` Jesper Juhl
2005-07-20 14:36 ` Jesper Juhl [this message]
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=9a874849050720073665b87c50@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=eliadl@013.net \
--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