public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: Joel Becker <Joel.Becker@oracle.com>
Cc: Andrew Morton <akpm@digeo.com>, linux-kernel@vger.kernel.org
Subject: Re: WimMark I report for 2.5.65-mm2 (now with deadline)
Date: Fri, 21 Mar 2003 18:19:49 +1100	[thread overview]
Message-ID: <3E7ABD15.1030005@cyberone.com.au> (raw)
In-Reply-To: <20030321024256.GW2835@ca-server1.us.oracle.com>

Joel Becker wrote:

>On Thu, Mar 20, 2003 at 05:58:05PM -0800, Andrew Morton wrote:
>
>>>WimMark I report for 2.5.65-mm2
>>>
>>>Runs (antic):  1374.22 1487.19 1437.26
>>>Runs (deadline):  1238.58 1537.36 1513.04
>>>
>>The averages of these are equal.  Can we safely conclude that this is fixed
>>up now?
>>
>
>	Not really, I think, because the 1238 seems a slightly fluke
>run.  I see these from time to time, but almost all of the deadline runs
>are in the 1500-1600 range.  In fact, -mm2 is lower than some other
>kernels by about 50 for deadline.
>	I wouldn't disagree with you if I didn't see that consistency.
>antic has never really jumped above 1500, and deadline almost never goes
>below.
>	Certainly they are much closer than they were.
>
The smaller first runs are not due to the benchmark running for the first
time, are they? In your mm1 tests you wrote:

>WimMark I report for 2.5.65-mm1
>
>Runs (antic):  1559.32 1025.38 1579.98
>Runs (deadline):  1554.48 1589.89 1350.37
>
So it does seem to be quite varied, but yes I'll keep working on it.
BTW. how do these results compare with 2.4 and other operating
systems on the same hardware, out of interest?


  reply	other threads:[~2003-03-21  7:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-20 20:40 WimMark I report for 2.5.65-mm2 (now with deadline) Joel Becker
2003-03-21  1:58 ` Andrew Morton
2003-03-21  2:42   ` Joel Becker
2003-03-21  7:19     ` Nick Piggin [this message]
2003-03-21 19:37       ` Joel Becker

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=3E7ABD15.1030005@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --cc=Joel.Becker@oracle.com \
    --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