public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <conman@kolivas.net>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, Ville Herva <vherva@niksula.hut.fi>,
	Daniel Jacobowitz <dan@debian.org>, Robert Love <rml@tech9.net>
Subject: Re: [BENCHMARK] gcc3.2 v 2.95.3 (contest and linux-2.5.38)
Date: Mon, 23 Sep 2002 15:13:08 +1000	[thread overview]
Message-ID: <1032757988.3d8ea2e4a0618@kolivas.net> (raw)
In-Reply-To: <3D8E988F.DCB3196D@digeo.com>

Quoting Andrew Morton <akpm@digeo.com>:

> Con Kolivas wrote:
> > 
> > Quoting Andrew Morton <akpm@digeo.com>:
> > 
> > > Con Kolivas wrote:
> > > >
> > > > Correct. contest was run with gcc2.95.3 only. The kernels were
> compiled
> > > with
> > > > 2.95.3 and 3.2 respectively.
> > >
> > > I think you made a mistake.  Please rerun. Just one data point will do.
> > >
> > 
> > Ok here are two points to confirm the results and their reproducibility:
> > 
> > No Load:
> > 2.5.38                  68.25           99%
> > 2.5.38-gcc32            103.03          99%
> > 2.5.38-gcc32a           103.47          99%
> > 
> > Process Load:
> > 2.5.38                  71.60           95%
> > 2.5.38-gcc32            112.98          91%
> > 2.5.38-gcc32a           113.60          91%
> > 
> 
> beats the hell out of me.  Frankly, I *still* think
> you made a mistake (at least on the io load thing)
> because the CPU time went down by a mile - it was
> waiting on disk all the time.

If you think I've made a mistake then you're probably correct. I'm investigating
this further. Please do NOT pass judgement on these benchmarks until I
completely retest everything, ensuring gcc is fixed for everything except the
kernel being tested. Disregard until I have a fresh set of confirmed results.

Con.

  parent reply	other threads:[~2002-09-23  5:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-23  3:04 [BENCHMARK] gcc3.2 v 2.95.3 (contest and linux-2.5.38) Con Kolivas
2002-09-23  3:10 ` Robert Love
2002-09-23  3:16   ` Con Kolivas
2002-09-23 11:06     ` Mark Veltzer
2002-09-23 13:56       ` Daniel Jacobowitz
2002-09-23  3:28 ` Robert Love
2002-09-23  3:41 ` Andrew Morton
2002-09-23  3:46   ` Daniel Jacobowitz
2002-09-23  3:50     ` Con Kolivas
     [not found]       ` <3D8E9158.4E3DE029@digeo.com>
     [not found]         ` <1032754853.3d8e96a520836@kolivas.net>
     [not found]           ` <3D8E988F.DCB3196D@digeo.com>
2002-09-23  5:13             ` Con Kolivas [this message]
2002-09-23  7:20               ` Axel H. Siebenwirth
2002-09-23  3:47   ` Robert Love

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=1032757988.3d8ea2e4a0618@kolivas.net \
    --to=conman@kolivas.net \
    --cc=akpm@digeo.com \
    --cc=dan@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@tech9.net \
    --cc=vherva@niksula.hut.fi \
    /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