public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <conman@kolivas.net>
To: Stan Bubrouski <stan@ccs.neu.edu>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [BENCHMARK] 2.5.51 with contest
Date: Wed, 11 Dec 2002 07:24:40 +1100	[thread overview]
Message-ID: <1039551880.3df64d88dc470@kolivas.net> (raw)
In-Reply-To: <3DF621D0.6040505@ccs.neu.edu>

Quoting Stan Bubrouski <stan@ccs.neu.edu>:

> Con Kolivas wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > 
> > Here are contest results (http://contest.kolivas.net) for 2.5.51 and
> related 
> > kerneles using the dedicated osdl (http://www.osdl.org) hardware. 
> > 
> > Uniprocessor:
> > noload:
> > Kernel [runs]           Time    CPU%    Loads   LCPU%   Ratio
> > 2.5.49 [5]              70.0    96      0       0       1.05
> > 2.5.50 [5]              69.9    96      0       0       1.05
> > 2.5.50-mm1 [5]          71.4    94      0       0       1.07
> > 2.5.51 [2]              69.8    96      0       0       1.05
> 
> I know this has been brought up before, but
> these don't seem to mean much unless you
> include 2.4.20 in the comaprison.

Repeated benchmarks of each successive release allow to detect subtle
differences of each change. If contest shows these changes the people who can
act on them will see them clearly if displayed only with relevant results. If
you want previous results, a full comparison is available at the full logs of
all previous benchmarks as I mention.

http://www.osdl.org/projects/ctdevel/results/

Con

      parent reply	other threads:[~2002-12-10 20:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-10 11:44 [BENCHMARK] 2.5.51 with contest Con Kolivas
2002-12-10 17:18 ` Stan Bubrouski
2002-12-10 18:45   ` Robert Love
2002-12-10 20:02     ` Stan Bubrouski
2002-12-10 20:51       ` Arador
2002-12-10 21:05       ` Robert Love
2002-12-10 20:24   ` 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=1039551880.3df64d88dc470@kolivas.net \
    --to=conman@kolivas.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stan@ccs.neu.edu \
    /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