From: Con Kolivas <kernel@kolivas.org>
To: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: [BENCHMARK] O1int patch with contest
Date: Sat, 28 Jun 2003 00:41:38 +1000 [thread overview]
Message-ID: <200306280041.47619.kernel@kolivas.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I've had some (off list) requests to see if the interactivity patch I posted
shows any differences in contest. To be honest I wasn't sure it would, and
this is not quite what I expected. Below is a 2.5.73-mm1 patched with
patch-O1int-0306271816 (2.5.73-O1i) compared to 2.5.73-mm1 with contest
(http://contest.kolivas.org).
no_load:
Kernel [runs] Time CPU% Loads LCPU% Ratio
2.5.73-O1i 1 78 93.6 0.0 0.0 1.00
2.5.73-mm1 1 77 94.8 0.0 0.0 1.00
cacherun:
Kernel [runs] Time CPU% Loads LCPU% Ratio
2.5.73-O1i 1 75 97.3 0.0 0.0 0.96
2.5.73-mm1 1 75 98.7 0.0 0.0 0.97
process_load:
Kernel [runs] Time CPU% Loads LCPU% Ratio
2.5.73-O1i 1 94 78.7 39.0 20.2 1.21
2.5.73-mm1 2 108 67.6 67.0 29.6 1.40
ctar_load:
Kernel [runs] Time CPU% Loads LCPU% Ratio
2.5.73-O1i 1 86 84.9 0.0 0.0 1.10
2.5.73-mm1 3 103 74.8 0.0 0.0 1.34
xtar_load:
Kernel [runs] Time CPU% Loads LCPU% Ratio
2.5.73-O1i 1 92 80.4 1.0 3.3 1.18
2.5.73-mm1 3 113 66.4 2.0 4.4 1.47
io_load:
Kernel [runs] Time CPU% Loads LCPU% Ratio
2.5.73-O1i 1 101 73.3 24.6 12.9 1.29
2.5.73-mm1 4 127 59.1 39.7 16.5 1.65
io_other:
Kernel [runs] Time CPU% Loads LCPU% Ratio
2.5.73-O1i 1 95 78.9 22.7 11.6 1.22
2.5.73-mm1 2 112 67.9 43.0 19.6 1.45
read_load:
Kernel [runs] Time CPU% Loads LCPU% Ratio
2.5.73-O1i 1 92 80.4 2.7 2.2 1.18
2.5.73-mm1 2 100 76.0 7.8 7.0 1.30
list_load:
Kernel [runs] Time CPU% Loads LCPU% Ratio
2.5.73-O1i 1 87 86.2 0.0 1.1 1.12
2.5.73-mm1 2 93 80.6 0.0 7.5 1.21
mem_load:
Kernel [runs] Time CPU% Loads LCPU% Ratio
2.5.73-O1i 1 84 86.9 35.0 1.2 1.08
2.5.73-mm1 2 114 68.4 54.0 1.8 1.48
dbench_load:
Kernel [runs] Time CPU% Loads LCPU% Ratio
2.5.73-O1i 1 222 33.3 2.0 31.5 2.85
2.5.73-mm1 4 365 20.8 5.0 48.2 4.74
I promise I didn't tune it with contest results in mind. There are still
things I want to do to it that may not affect these results.
Con
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE+/FekF6dfvkL3i1gRAhHUAJwOiLq+u3nEGn9Ym+c5x4JpTqrK1ACfX79F
WKLTsbtqwXyFpOZ+i+JvgVU=
=nQk2
-----END PGP SIGNATURE-----
next reply other threads:[~2003-06-27 14:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-27 14:41 Con Kolivas [this message]
2003-06-27 15:28 ` [BENCHMARK] O1int patch with contest Felipe Alfaro Solana
2003-06-27 15:40 ` Con Kolivas
2003-06-27 23:38 ` Roberto Orenstein
2003-06-27 23:11 ` Nick Piggin
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=200306280041.47619.kernel@kolivas.org \
--to=kernel@kolivas.org \
--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