From: Con Kolivas <conman@kolivas.net>
To: Andrew Morton <akpm@digeo.com>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [BENCHMARK] 2.5.43-mm2 with contest
Date: Thu, 17 Oct 2002 20:56:38 +1000 [thread overview]
Message-ID: <200210172056.45002.conman@kolivas.net> (raw)
In-Reply-To: <3DAE6E63.EFAF0F80@digeo.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thursday 17 Oct 2002 6:01 pm, Andrew Morton wrote:
> Con Kolivas wrote:
> > Here are the updated benchmarks with contest v0.51
> > (http://contest.kolivas.net) showing the change from -mm1 to -mm2. Other
> > results removed for clarity.
> >
> > noload:
> > Kernel [runs] Time CPU% Loads LCPU% Ratio
> > 2.4.18 [3] 71.8 93 0 0 1.01
> > 2.5.43 [2] 74.6 92 0 0 1.04
> > 2.5.43-mm1 [4] 74.9 93 0 0 1.05
> > 2.5.43-mm2 [2] 73.4 93 0 0 1.03
>
> Would be interesting to run
>
> blockdev --setra 1024 /dev/hdXX
>
> here. We're getting more idle time with 2.5 and that can only
> be due to disk wait - the IO scheduler changes. This might make a
> small difference.
Well that isn't it (b is with ra 1024):
2.5.43-mm2 [2] 73.4 93 0 0 1.03
2.5.43-mm2b [3] 76.4 94 0 0 1.07
>
> > ...
> > Removal of per-cpu pages patch does not seem to have been detrimental to
> > contest benchmarks at least - perhaps this is responsible for the noload
> > being better now?
>
> Well that code is still there. I'd expect a very small benefit from it
> in this testing.
Sorry. Misunderstood your announce message.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9rpdrF6dfvkL3i1gRAu5AAJ9B3LJ3kuplNHdhJGsW785CJ2i4GgCfRs9W
d2BW4cSQaanL/FjJTu3gU9k=
=+Foh
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2002-10-17 10:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-17 7:40 Con Kolivas
2002-10-17 8:01 ` Andrew Morton
2002-10-17 10:56 ` Con Kolivas [this message]
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=200210172056.45002.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
all inboxes | Powered by JetHome®