From: Andrew Morton <akpm@digeo.com>
To: Joel Becker <Joel.Becker@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: WimMark I report for 2.5.69
Date: Wed, 7 May 2003 15:41:50 -0700 [thread overview]
Message-ID: <20030507154150.005db55e.akpm@digeo.com> (raw)
In-Reply-To: <20030507175422.GX3989@ca-server1.us.oracle.com>
Joel Becker <Joel.Becker@oracle.com> wrote:
>
> WimMark I report for 2.5.69
>
> Runs: 1462.17 1005.78 1995.99
> ...
> This benchmark is sensitive to random system events.
You can say that again.
> I run three runs because of this. If two runs are nearly identical and the
> remaining run is way off, that run should probably be ignored (it is
> often a low number, signifying that something on the system impacted
> the benchmark).
Here we have 1.0, 1.5 and 2.0.
We need to understand why there is such variation. If we can do that,
then perhaps we can make those 1.0's and 1.5's go away.
Is that a thing you can work on? One approach would be to vary parameters
(filesystem type, amount of memory, TCQ lengths, workload, whatever) and
see which ones the throughput is sensitive to.
next prev parent reply other threads:[~2003-05-07 22:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-07 17:54 WimMark I report for 2.5.69 Joel Becker
2003-05-07 22:41 ` Andrew Morton [this message]
2003-05-07 23:19 ` Joel Becker
2003-05-07 23:28 ` Andrew Morton
2003-05-07 23:58 ` 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=20030507154150.005db55e.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=Joel.Becker@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.