mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Con Kolivas <conman@kolivas.net>
To: linux-kernel@vger.kernel.org
Cc: axboe@suse.de, Andrew Morton <akpm@digeo.com>
Subject: [BENCHMARK] 2.5.38-mm2 contest results
Date: Mon, 23 Sep 2002 17:24:14 +1000	[thread overview]
Message-ID: <1032765854.3d8ec19e18afb@kolivas.net> (raw)



Here follow the contest benchmarks for 2.5.38-mm2

NoLoad:
Kernel                  Time            CPU
2.4.19                  66.56           99%
2.5.38                  68.25           99%
2.5.38-mm1              67.17           99%
2.5.38-mm2              67.48           99%

Process Load:
Kernel                  Time            CPU
2.4.19                  81.29           80%
2.5.38                  71.60           95%
2.5.38-mm1              70.49           95%
2.5.38-mm2              70.82           95%

IO Half Load:
Kernel                  Time            CPU
2.4.19                  101.39          69%
2.5.38                  81.26           90%
2.5.38-mm1              82.52           87%
2.5.38-mm2              78.46           91%

IO Full Load:
Kernel                  Time            CPU
2.4.19                  170.70          41%
2.5.38                  170.21          42%
2.5.38-mm1              434.41          16%
2.5.38-mm2              108.15          66%

Mem Load:
Kernel                  Time            CPU
2.4.19                  93.33           77%
2.5.38                  104.22          70%
2.5.38-mm1              92.97           77%
2.5.38-mm2              90.89           80%

As akpm has said, mm2 should fix the write starves read problem in mm2 and this
is clearly shown in the IO full load results being substantially better.
This is on an IDE system. 

Other results removed for clarity. All tests are done with gcc2.95.3 :\

Con.

                 reply	other threads:[~2002-09-23  7:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1032765854.3d8ec19e18afb@kolivas.net \
    --to=conman@kolivas.net \
    --cc=akpm@digeo.com \
    --cc=axboe@suse.de \
    --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

all inboxes | Powered by JetHome®