From: Joel Becker <Joel.Becker@oracle.com>
To: Nick Piggin <piggin@cyberone.com.au>
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 11:37:12 -0800 [thread overview]
Message-ID: <20030321193711.GA31586@ca-server1.us.oracle.com> (raw)
In-Reply-To: <3E7ABD15.1030005@cyberone.com.au>
On Fri, Mar 21, 2003 at 06:19:49PM +1100, Nick Piggin wrote:
> The smaller first runs are not due to the benchmark running for the first
> time, are they? In your mm1 tests you wrote:
The benchmark has a ramp-up period built-in to populate the
database caches. The first run is not always the slowest.
The thing is, the runs can be sensitive to some things (someone
logs in and runs something, Linux decides to flush some cache, etc).
The runs take long enough without extending them to flatten this some.
> >Runs (antic): 1559.32 1025.38 1579.98
> >Runs (deadline): 1554.48 1589.89 1350.37
If you notice, the variance always is of a fluke sort. This is
why I do multiple runs. The non-fluke runs are very consistent. See
runs 1 and 3 for antic and 1 and 2 for deadline in the quote.
> 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?
I've not run other operating systems, as I don't have the
software or OSes installed. I've not run a vanilla 2.4 recently, and
probably should do that.
Joel
--
"I'm living so far beyond my income that we may almost be said
to be living apart."
- e e cummings
Joel Becker
Senior Member of Technical Staff
Oracle Corporation
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127
prev parent reply other threads:[~2003-03-21 19:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-20 20:40 Joel Becker
2003-03-21 1:58 ` Andrew Morton
2003-03-21 2:42 ` Joel Becker
2003-03-21 7:19 ` Nick Piggin
2003-03-21 19:37 ` Joel Becker [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=20030321193711.GA31586@ca-server1.us.oracle.com \
--to=joel.becker@oracle.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
/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
all inboxes | Powered by JetHome®