mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 16:28:30 -0700	[thread overview]
Message-ID: <20030507162830.47af1d47.akpm@digeo.com> (raw)
In-Reply-To: <20030507231919.GA3989@ca-server1.us.oracle.com>

Joel Becker <Joel.Becker@oracle.com> wrote:
>
> On Wed, May 07, 2003 at 03:41:50PM -0700, Andrew Morton wrote:
> > > Runs:  1462.17 1005.78 1995.99
> > > ...
> > > This benchmark is sensitive to random system events.
> > 
> > You can say that again.
> > 
> > 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.
> 
> 	Some kernels run very very even.  Others do not.  I suspect that
> certain kernel behaviors and changes exacerbate the issues.

Correct me if I'm wrong, but this test is largely seek-bound, is it not?

Do you monitor the total CPU utilisation during the run?  Is it generally
low?  If so then we're seek-bound.

File layout will influence things a lot.  Small variations in timing and in
CPU scheduler activity could well cause significant dfifferences in file
layout.

Does the test generate the files on-the-fly, or are they laid out
beforehand?

Is it possible to fully populate the datafiles before the run, with a
single thread of control?  That will ensure that each run is working off
the same layout and will give a better basis for comparison.

It will also tell us that some layout tweaks may be needed.

  reply	other threads:[~2003-05-07 23:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-07 17:54 Joel Becker
2003-05-07 22:41 ` Andrew Morton
2003-05-07 23:19   ` Joel Becker
2003-05-07 23:28     ` Andrew Morton [this message]
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=20030507162830.47af1d47.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 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®