From: Con Kolivas <conman@kolivas.net>
To: linux kernel mailing list <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@digeo.com>
Subject: [BENCHMARK] 2.5.44-mm1 with contest
Date: Mon, 21 Oct 2002 14:15:59 +1000 [thread overview]
Message-ID: <1035173759.3db37f7f3c495@kolivas.net> (raw)
Here are contest 0.51 benchmarks for 2.5.44-mm1 with shared pagetables enabled:
noload:
Kernel [runs] Time CPU% Loads LCPU% Ratio
2.5.43-mm2 [2] 73.4 93 0 0 1.03
2.5.44 [3] 74.6 93 0 0 1.04
2.5.44-mm1 [3] 75.0 93 0 0 1.05
process_load:
Kernel [runs] Time CPU% Loads LCPU% Ratio
2.5.43-mm2 [2] 105.8 71 44 31 1.48
2.5.44 [3] 90.9 76 32 26 1.27
2.5.44-mm1 [3] 191.5 36 168 64 2.68
These were all checked to ensure it was not one pathological run making the
value high. The range was 190.6->192.7.
ctar_load:
Kernel [runs] Time CPU% Loads LCPU% Ratio
2.5.43-mm2 [1] 92.3 82 1 5 1.29
2.5.44 [3] 97.7 80 1 6 1.37
2.5.44-mm1 [3] 99.2 78 1 6 1.39
xtar_load:
Kernel [runs] Time CPU% Loads LCPU% Ratio
2.5.43-mm2 [2] 171.0 45 2 8 2.39
2.5.44 [3] 117.0 65 1 7 1.64
2.5.44-mm1 [3] 156.2 49 2 7 2.19
io_load:
Kernel [runs] Time CPU% Loads LCPU% Ratio
2.5.43-mm2 [2] 301.1 26 21 11 4.22
2.5.44 [3] 873.8 9 69 12 12.24
2.5.44-mm1 [3] 347.3 22 35 15 4.86
read_load:
Kernel [runs] Time CPU% Loads LCPU% Ratio
2.5.43-mm2 [1] 105.7 73 6 4 1.48
2.5.44 [3] 110.8 68 6 3 1.55
2.5.44-mm1 [3] 110.5 69 7 3 1.55
list_load:
Kernel [runs] Time CPU% Loads LCPU% Ratio
2.5.43-mm2 [1] 98.9 72 1 23 1.39
2.5.44 [3] 99.1 71 1 21 1.39
2.5.44-mm1 [3] 96.5 74 1 22 1.35
mem_load:
Kernel [runs] Time CPU% Loads LCPU% Ratio
2.5.43-mm2 [2] 106.5 69 27 2 1.49
2.5.44 [3] 114.3 67 30 2 1.60
2.5.44-mm1 [3] 159.7 47 38 2 2.24
Notably different results in many places. This is a similar pattern to the last
time I enabled shared pagetables. I haven't had the time to try without it
enabled yet.
Con
next reply other threads:[~2002-10-21 4:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 4:15 Con Kolivas [this message]
2002-10-21 5:28 ` Andrew Morton
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=1035173759.3db37f7f3c495@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome