public inbox for linux-kernel@vger.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, Nick Piggin <piggin@cyberone.com.au>
Subject: Re: [BENCHMARK] 2.5.59{-mm2} with contest
Date: Sat, 18 Jan 2003 13:47:01 -0800	[thread overview]
Message-ID: <20030118134701.555c9728.akpm@digeo.com> (raw)
In-Reply-To: <200301190051.13781.conman@kolivas.net>

Con Kolivas <conman@kolivas.net> wrote:
>
> io_load:
> Kernel     [runs]       Time    CPU%    Loads   LCPU%   Ratio
> 2.5.58          3       136     58.8    6       12.4    1.84
> 2.5.58-mm1      3       138     55.8    7       13.0    1.86
> 2.5.59          4       113     68.1    4       9.7     1.53
> 2.5.59-mm2      3       563     12.8    38      17.4    7.61

I don't see such gross variations here, and there's nothing between -mm1 and
-mm2 which could cause this.  (BTW: what idiot broke diffstat as distributed
in rh8.0?  It fails to understand interdiff output, which is quite
legitimately formatted).

However there are some interesting snippets.  Elapsed time for io_load:

2.5.59: 					182,183,180
2.5.59 + deadline-np-42:			198,114,106,112,183,140
2.5.59 + deadline-np-42 + deadline-np-43:	224,224
2.5.59-mm2:					212,239

So it looks like deadline-np-42.patch lessens starvation of reads by writes,
and deadline-np-43.patch considerably worsens it.

But this is all just fiddling around.  Nick is working on an implementation
of anticipatory scheduling, which is a whole new ball game.  The pressure is
on ;)



      reply	other threads:[~2003-01-18 21:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-18 13:50 [BENCHMARK] 2.5.59{-mm2} with contest Con Kolivas
2003-01-18 21:47 ` Andrew Morton [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=20030118134701.555c9728.akpm@digeo.com \
    --to=akpm@digeo.com \
    --cc=conman@kolivas.net \
    --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