All of lore.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <conman@kolivas.net>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@digeo.com>
Subject: [BENCHMARK] 2.5.39-mm1
Date: Mon, 30 Sep 2002 19:41:37 +1000	[thread overview]
Message-ID: <200209301941.41627.conman@kolivas.net> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Here follow the contest v0.41 (http://contest.kolivas.net) results for 
2.5.39-mm1:

noload:
Kernel                  Time            CPU             Ratio
2.4.19                  67.71           98%             1.00
2.5.38                  72.38           94%             1.07
2.5.38-mm3              73.00           93%             1.08
2.5.39                  73.17           93%             1.08
2.5.39-mm1              72.97           94%             1.08

process_load:
Kernel                  Time            CPU             Ratio
2.4.19                  110.75          57%             1.64
2.5.38                  85.71           79%             1.27
2.5.38-mm3              96.32           72%             1.42
2.5.39                  88.9            75%             1.33*
2.5.39-mm1              99.0            69%             1.45*

io_load:
Kernel                  Time            CPU             Ratio
2.4.19                  216.05          33%             3.19
2.5.38                  887.76          8%              13.11
2.5.38-mm3              105.17          70%             1.55
2.5.39                  229.4           34%             3.4
2.5.39-mm1              239.5           33%             3.4

mem_load:
Kernel                  Time            CPU             Ratio
2.4.19                  105.40          70%             1.56
2.5.38                  107.89          73%             1.59
2.5.38-mm3              117.09          63%             1.73
2.5.39                  103.72          72%             1.53
2.5.39-mm1              104.61          73%             1.54

process_load and io_load results are averages of 6 runs.

Statistical significance in process_load performance (p=0.017), with mm1 
slower. The other changes did not show statistical significance, with trends 
as noted above.

note: these were done with the temporary fix for the reiserfs breakage but as 
far as I'm aware it shouldn't affect this test

Hardware: 1133MhzP3, 224Mb Ram, IDE-ATA100 5400rpm drive with io_load tested 
on same disk, reiserFS. Preempt=N for all kernels.

Con
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9mBxUF6dfvkL3i1gRAr4kAJ47cICW0qIXLmswyBL9t1ZsiyxgVwCfaHCN
bXOSrZtwTjJsSibiBm5KrRo=
=XWpt
-----END PGP SIGNATURE-----

             reply	other threads:[~2002-09-30  9:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-30  9:41 Con Kolivas [this message]
2002-09-30 19:36 ` [BENCHMARK] 2.5.39-mm1 Andrew Morton
2002-09-30 20:36   ` Con Kolivas
2002-10-01 10:16     ` Jens Axboe
2002-10-01 10:15   ` Jens Axboe
     [not found]     ` <3D9976D9.C06466B@digeo.com>
2002-10-01 12:19       ` Con Kolivas
2002-10-01 12:30         ` Jens Axboe
2002-10-01 13:44           ` Con Kolivas
2002-10-01 15:49             ` Jens Axboe
2002-10-01 23:41               ` jw schultz
     [not found]       ` <5.1.0.14.2.20021001190123.00b3cdc8@pop.gmx.net>
     [not found]         ` <20021001172200.GH5755@suse.de>
2002-10-02  2:55           ` Con Kolivas

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=200209301941.41627.conman@kolivas.net \
    --to=conman@kolivas.net \
    --cc=akpm@digeo.com \
    --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 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.