From: "Paolo Ciarrocchi" <ciarrocchi@linuxmail.org>
To: <riel@conectiva.com.br>
Cc: conman@kolivas.net, <linux-kernel@vger.kernel.org>
Subject: Re: Combined performance patches update for 2.4.19
Date: Sun, 25 Aug 2002 20:33:34 +0800 [thread overview]
Message-ID: <20020825123334.460.qmail@linuxmail.org> (raw)
From: Rik van Riel <riel@conectiva.com.br>
[...]
> > Maybe I can find the time to run a few tests, can anyone suggest me an
> > "intersting" test?
>
> Bob Matthews has a benchmark called irman, which tries to measure
> response time during a number of background loads.
>
> I'm not sure it is too interesting in this case, though. People
> don't really care about the exact latency of sub-millisecond
> responses (should be the vast majority) but about the few times
> per minute where their mp3 skips.
>
> Simple averages won't show the mp3 skips, because the number of
> fast responses are bound to be hundreds of thousands of times
> more common then the "mp3 skipping hickups".
>
> Maybe the histogram mode of irman might show something useful ?
>
> (then again, maybe it doesn't ... haven't tried yet)
>
> http://people.redhat.com/bmatthews/irman/
Well... I tried irman, and here it goes the results:
Test: NULL
Kernel max min avg stddev
2.4.18 45.955 0.004 0.005 0.061
2.4.18-0.24pre3 0.121 0.005 0.005 0.001
2.4.19 1.683 0.005 0.005 0.002
2.4.19-ck3 1.694 0.005 0.005 0.002
2.4.19-ck3-aa 0.200 0.005 0.005 0.001
2.4.19-ck3-rmap 1.628 0.005 0.005 0.002
2.5.31 1.636 0.006 0.007 0.002
Test: MEMORY
Kernel max min avg stddev
2.4.18 69.471 0.005 0.010 0.554
2.4.18-0.24pre3 70.031 0.005 0.010 0.546
2.4.19 60.058 0.005 0.011 0.558
2.4.19-ck3 150.216 0.005 0.009 0.720
2.4.19-ck3-aa 150.075 0.005 0.008 0.621
2.4.19-ck3-rmap 150.059 0.005 0.009 0.674
2.5.31 1.823 0.005 0.007 0.002
Test: FILE_IO
Kernel max min avg stddev
2.4.18 190.042 0.005 0.019 1.452
2.4.18-0.24pre3 325.509 0.005 0.017 1.379
2.4.19 190.033 0.005 0.022 1.525
2.4.19-ck3 1050.048 0.005 0.015 2.196
2.4.19-ck3-aa 1363.153 0.005 0.014 2.177
2.4.19-ck3-rmap 450.073 0.005 0.016 2.097
2.5.31 610.021 0.006 0.019 2.314
Test: PROCESS
Kernel max min avg stddev
2.4.18 350.056 0.005 0.068 2.548
2.4.18-0.24pre3 270.138 0.005 0.068 2.439
2.4.19 270.238 0.005 0.075 2.594
2.4.19-ck3 1710.017 0.005 0.022 4.293
2.4.19-ck3-aa 1620.023 0.005 0.023 4.298
2.4.19-ck3-rmap 1630.020 0.005 0.025 4.724
2.5.31 1171.021 0.006 0.026 4.354
Ciao,
Paolo
--
Get your free email from www.linuxmail.org
Powered by Outblaze
next reply other threads:[~2002-08-25 12:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-25 12:33 Paolo Ciarrocchi [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-24 18:58 Combined performance patches update for 2.4.19 Paolo Ciarrocchi
2002-08-24 20:56 ` Rik van Riel
2002-08-27 22:48 ` Cliff White
[not found] <20020824120208.30967.qmail@linuxmail.org>
2002-08-24 12:21 ` conman
[not found] <20020823233128.20631.qmail@linuxmail.org>
2002-08-24 0:53 ` conman
[not found] <Pine.LNX.4.44L.0208231012530.1857-100000@imladris.surriel.com>
2002-08-23 14:10 ` conman
2002-08-23 15:52 ` Rik van Riel
2002-08-23 12:38 conman
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=20020825123334.460.qmail@linuxmail.org \
--to=ciarrocchi@linuxmail.org \
--cc=conman@kolivas.net \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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