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.54-mm3 with contest
Date: Sun, 5 Jan 2003 23:33:04 +1100 [thread overview]
Message-ID: <200301052333.20853.conman@kolivas.net> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Here are contest benchmarks for the -mm* series (offline for holidays and with
a mem leak so no results for mm1/2)
noload:
Kernel [runs] Time CPU% Loads LCPU% Ratio
2.5.53 [7] 70.1 96 0 0 1.05
2.5.53-mm1 [7] 71.0 96 0 0 1.06
2.5.54 [5] 70.0 96 0 0 1.05
2.5.54-mm3 [5] 70.1 96 0 0 1.05
cacherun:
Kernel [runs] Time CPU% Loads LCPU% Ratio
2.5.53 [7] 67.6 99 0 0 1.01
2.5.53-mm1 [7] 68.5 99 0 0 1.03
2.5.54 [5] 67.6 99 0 0 1.01
2.5.54-mm3 [5] 67.5 99 0 0 1.01
process_load:
Kernel [runs] Time CPU% Loads LCPU% Ratio
2.5.53 [7] 86.9 77 18 21 1.30
2.5.53-mm1 [7] 117.1 58 47 40 1.75
2.5.54 [5] 85.5 78 17 19 1.28
2.5.54-mm3 [5] 87.2 77 18 21 1.31
Whatever that change was in .53-mm1 has reverted back to previous results
dbench_load:
Kernel [runs] Time CPU% Loads LCPU% Ratio
2.5.54 [5] 216.8 37 2 52 3.25
2.5.54-mm3 [5] 195.7 39 2 48 2.93
ctar_load:
Kernel [runs] Time CPU% Loads LCPU% Ratio
2.5.53 [7] 107.4 81 3 9 1.61
2.5.53-mm1 [7] 103.1 79 3 10 1.54
2.5.54 [4] 102.7 82 3 9 1.54
2.5.54-mm3 [5] 103.8 81 3 9 1.55
xtar_load:
Kernel [runs] Time CPU% Loads LCPU% Ratio
2.5.53 [7] 151.0 69 3 8 2.26
2.5.53-mm1 [7] 150.2 66 2 7 2.25
2.5.54 [4] 159.3 71 3 8 2.39
2.5.54-mm3 [5] 124.1 69 2 7 1.86
speedup here
io_load:
Kernel [runs] Time CPU% Loads LCPU% Ratio
2.5.53 [7] 113.9 63 12 12 1.71
2.5.53-mm1 [7] 133.1 57 23 17 1.99
2.5.54 [4] 121.0 61 13 12 1.81
2.5.54-mm3 [5] 128.6 57 15 13 1.93
io_other:
Kernel [runs] Time CPU% Loads LCPU% Ratio
2.5.53 [7] 99.5 73 8 10 1.49
2.5.53-mm1 [7] 107.7 70 18 17 1.61
2.5.54 [4] 96.0 74 8 9 1.44
2.5.54-mm3 [5] 99.8 71 9 11 1.49
read_load:
Kernel [runs] Time CPU% Loads LCPU% Ratio
2.5.53 [7] 88.2 80 15 6 1.32
2.5.53-mm1 [7] 89.6 80 12 6 1.34
2.5.54 [4] 87.7 81 14 6 1.31
2.5.54-mm3 [5] 91.5 77 13 6 1.37
list_load:
Kernel [runs] Time CPU% Loads LCPU% Ratio
2.5.53 [7] 81.5 85 0 9 1.22
2.5.53-mm1 [7] 82.1 85 0 9 1.23
2.5.54 [4] 81.3 85 0 9 1.22
2.5.54-mm3 [5] 81.4 85 0 9 1.22
mem_load:
Kernel [runs] Time CPU% Loads LCPU% Ratio
2.5.53 [7] 98.7 80 44 2 1.48
2.5.53-mm1 [7] 110.9 67 41 1 1.66
2.5.54 [4] 98.2 80 45 2 1.47
2.5.54-mm3 [5] 108.7 70 46 2 1.63
Con
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)
iD8DBQE+GCYAF6dfvkL3i1gRAsCIAJ92Fdq4L/KouJ+KCmxn68lSXw7jXACgojkb
xFpknpj5NhTKYFpG07w818M=
=SD7Z
-----END PGP SIGNATURE-----
reply other threads:[~2003-01-05 12:24 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=200301052333.20853.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox