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] 2.5.42-mm2 contest results
Date: Sun, 13 Oct 2002 13:53:03 -0700	[thread overview]
Message-ID: <3DA9DD2F.E5A20CD2@digeo.com> (raw)
In-Reply-To: 200210132128.13752.conman@kolivas.net

Con Kolivas wrote:
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Here are the surprisingly different results from 2.5.42-mm2 with the contest
> benchmark (http://contest.kolivas.net). This was run with pagetable sharing
> enabled. Older results hidden for clarity.
> 
> noload:
> Kernel [runs]           Time    CPU%    Loads   LCPU%   Ratio
> 2.5.41-mm3 [1]          74.4    93      0       0       1.11
> 2.5.42 [2]              72.5    93      0       0       1.08
> 2.5.42-mm2 [3]          79.0    92      0       0       1.18
> 

Well something is burning CPU there, and I do not know what it is.
Things are normal here:

With 2.5.42-mm2++, shared pagetables enabled:
make -j6 bzImage  416.97s user 33.94s system 374% cpu 2:00.28 total

With 2.5.42+last night's BK:
make -j6 bzImage  416.09s user 33.04s system 370% cpu 2:01.15 total

With 2.5.42:
make -j6 bzImage  416.56s user 32.49s system 375% cpu 1:59.69 total

So.  Could you please profile the `noload' run?  Just enable oprofile
and local IO APIC and do:

- add "idle=poll" to your kernel boot commandline
- sudo rm -rf /var/lib/oprofile
- sudo op_start --vmlinux=/boot/vmlinux --ctr0-event=CPU_CLK_UNHALTED \
  --ctr0-count=600000
- time make -j4 bzImage ; sudo op_stop
- oprofpp -l -i /boot/vmlinux
- sudo killall oprofiled

(Do the `make' quickly after the op_start to avoid bogus idle time).

Thanks.

      reply	other threads:[~2002-10-13 20:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-13 11:27 [BENCHMARK] 2.5.42-mm2 contest results Con Kolivas
2002-10-13 20:53 ` Andrew Morton [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=3DA9DD2F.E5A20CD2@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