All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: szonyi calin <caszonyi@yahoo.com>
Cc: linux-kernel@vger.kernel.org, rml@tech9.net
Subject: Re: Q:Howto benchmark preemptible kernel ?
Date: Wed, 07 Nov 2001 12:29:06 -0800	[thread overview]
Message-ID: <3BE99992.A6BD18F4@zip.com.au> (raw)
In-Reply-To: <20011107165153.91027.qmail@web13105.mail.yahoo.com>

szonyi calin wrote:
> 
> Hi
> I'm have a Cyrix 486/66 with 12Megs of ram.
> I'm using preemptible patches from quite some time
> now.
> (2.4.10- 2.4.13)
> I was using both Robert Love and Andrew Morton's
> patch.
> I would like to do some benhmarks but there are some
> issues:
> 1. The system is slow and has low memory so a big
> benchmark is out of question (compiling the kernel
> take 4 hours if i don't touch the console)
> 2. The benchmark must be small and adequate (patching
> the kernel to make a benchmark is out of discussion)
> 
> Any ideas ?
> 

None of these patches make any significant difference
to throughput of anything, really.

If you have a particular latency-sensitive application then
that's the thing which you should be testing with.

There's a modified version of Mark Hahn's `realfeel' app in 
http://www.uow.edu.au/~andrewm/linux/amlat.tar.gz
which I find to be a convenient way of quantitatively
determining latencies.  There are some grubby scripts
in there which create graphical output too.

 
> P.S. (for Andrew ) Will there be a patch for 2.4.14 ?

J Sloan was the first to send me an updated patch this time.
Thanks!

It needs a bit of maintenance at present - last time I gave it
a good beating (a couple of weeks ago) there were a couple of
ten millisecond blips.

-

  reply	other threads:[~2001-11-07 20:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-07 16:51 Q:Howto benchmark preemptible kernel ? szonyi calin
2001-11-07 20:29 ` Andrew Morton [this message]
2001-11-08 10:20   ` szonyi calin

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=3BE99992.A6BD18F4@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=caszonyi@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@tech9.net \
    /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.