mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Con Kolivas <conman@kolivas.net>
To: linux-kernel@vger.kernel.org
Subject: [BENCHMARK] Preempt effect on 2.5.39 with contest 0.41
Date: Sun, 29 Sep 2002 12:43:27 +1000	[thread overview]
Message-ID: <1033267407.3d9668cf555f2@kolivas.net> (raw)

I've performed some benchmarks with the latest contest v0.41
(http://contest.kolivas.net) to determine what effect preemptible has on these
benchmarks and whether contest has the ability to show any effect.

Here are the benchmarks:

noload:
Kernel                  Time            CPU             Ratio
2.5.39                  73.17           93%             1.08
2.5.39-pe               73.03           94%             1.08

process_load:
Kernel                  Time            CPU             Ratio
2.5.39                  91.0            76%             1.31*
2.5.39-pe               83.6            82%             1.23

io_load:
Kernel                  Time            CPU             Ratio
2.5.39                  226             37%             3.20
2.5.39-pe               234             34%             3.43

mem_load:
Kernel                  Time            CPU             Ratio
2.5.39                  103.72          72%             1.53
2.5.39-pe               103.95          73%             1.54

The only statistically significant difference was in process_load where enabling
preempt made it faster. Well duh, what else what you expect? At least we can see
it is having the desired effect and not detrimental to any other area, and that
contest is able to show this effect.

Average of 5 runs when difference was noted, simplified for clarity.

Con.

             reply	other threads:[~2002-09-29  2:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-29  2:43 Con Kolivas [this message]
2002-09-29  5:09 Dieter Nützel
2002-09-29  5:59 ` 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=1033267407.3d9668cf555f2@kolivas.net \
    --to=conman@kolivas.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

all inboxes | Powered by JetHome®