public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Con Kolivas <conman@kolivas.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BENCHMARK] gcc3.2 v 2.95.3 (contest and linux-2.5.38)
Date: Sun, 22 Sep 2002 20:41:51 -0700	[thread overview]
Message-ID: <3D8E8D7F.810EF57F@digeo.com> (raw)
In-Reply-To: 1032750261.3d8e84b5486a9@kolivas.net

Con Kolivas wrote:
> 
> I performed contest benchmarks on kernel 2.5.38 when the kernel is compiled with
> gcc3.2 to gcc2.95.3
> 
> warning: The following benchmarks may be disturbing to some viewers:
> 
> No Load:
> Kernel                  Time            CPU
> 2.5.38                  68.25           99%
> 2.5.38-gcc32            103.03          99%
> 

Try gcc-2.91.66.  It might break the 45 second mark.

> IO Full Load:
> Kernel                  Time            CPU
> 2.5.38                  170.21          42%
> 2.5.38-gcc32            1405.25         8%

The streaming write is stalling gcc's read for long enough for gcc's
working set to be evicted.  And the working set cannot be reestablished
because the streaming write prevents it.  Meltdown.

I have fixed this.  Hang around.

  parent reply	other threads:[~2002-09-23  3:36 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 [this message]
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
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=3D8E8D7F.810EF57F@digeo.com \
    --to=akpm@digeo.com \
    --cc=conman@kolivas.net \
    --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