All of lore.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.59-mm7 with contest
Date: Fri, 31 Jan 2003 18:04:42 -0800	[thread overview]
Message-ID: <20030131180442.06e39ffc.akpm@digeo.com> (raw)
In-Reply-To: <200302011013.36125.conman@kolivas.net>

Con Kolivas <conman@kolivas.net> wrote:
>
> On Saturday 01 Feb 2003 10:01 am, Andrew Morton wrote:
> > Con Kolivas wrote:
> > > ...
> > > io_load:
> > > Kernel     [runs]       Time    CPU%    Loads   LCPU%   Ratio
> > > 2.5.59          3       153     50.3    8       13.7    1.94
> > > 2.5.59-mm6      2       90      83.3    2       6.7     1.15
> > > 2.5.59-mm7      5       110     68.2    2       6.4     1.41
> > > read_load:
> > > Kernel     [runs]       Time    CPU%    Loads   LCPU%   Ratio
> > > 2.5.59          3       102     76.5    5       4.9     1.29
> > > 2.5.59-mm6      3       733     10.8    56      6.3     9.40
> > > 2.5.59-mm7      4       90      84.4    1       1.3     1.15
> >
> > The background loads took some punishment.
> 
> Yes and I'd say a ratio of only 1.15 suggests kernel compilation got an unfair 
> share of the resources.

A very important metric is system-wide idle/IO-wait CPU time.  As long as
that is kept nice and low, we can then finetune the starvation and fairness
aspects.


  reply	other threads:[~2003-02-01  1:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-31 22:30 [BENCHMARK] 2.5.59-mm7 with contest Con Kolivas
2003-01-31 23:01 ` Andrew Morton
2003-01-31 23:13   ` Con Kolivas
2003-02-01  2:04     ` Andrew Morton [this message]
2003-02-01  0:37 ` Nick Piggin
2003-02-01  0:44   ` Con Kolivas
     [not found]     ` <3E3B1B1E.7050800@cyberone.com.au>
2003-02-01  1:09       ` Con Kolivas
2003-02-01  1:23         ` Nick Piggin
2003-02-01  3:21           ` Con Kolivas

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=20030131180442.06e39ffc.akpm@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 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.