The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: "Diego Calleja García" <diegocg@teleline.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: benchmark: 2.5 io test regression?
Date: Thu, 10 Jul 2003 13:27:55 +1000	[thread overview]
Message-ID: <3F0CDD3B.4080408@cyberone.com.au> (raw)
In-Reply-To: <20030710013600.1483e80a.diegocg@teleline.es>



Diego Calleja García wrote:

>Hi. I just went to my 2.5 kernel source tree and i did
>
>#time grep foo * -r
>
>in both 2.4 & 2.5
>
>doing this in 2.4 takes:
>real    0m50.614s
>user    0m1.150s
>sys     0m2.560s
>
>2.5.74-mm3 AS:
>real    0m46.207s
>user    0m1.156s
>sys     0m3.161s
>
>2.5.74-mm3 deadline:
>real    0m57.418s
>user    0m1.160s
>sys     0m3.107s
>
>I repeated the tests and they show very similar numbers. One time 2.4 was faster
>than 2.5 with AS.
>Hardware is p3 2x800 UDMA 100 7200 rpm 2 MB ide disk, filesystem ext3 (default
>mount options). DMA was activated in both 2.4 and 2.5.
>
>
>Should 2.5 be faster here, or it's the expected behaviour? I'd
>have expected a bit more of AS, but perhaps AS it isn't good for
>this benchmark?
>

This test won't exercise the IO scheduler at all - in any kernel.
It only gets 1 read request at a time. Any differences you see
might be due to something happening in the background or just
random variations. If you want to see AS really work, do something
like this in the background, then time your grep.

while true;
do dd if=/dev/zero of=./temp bs=1M count=(the size of your ram);
done



  reply	other threads:[~2003-07-10  3:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-09 23:36 benchmark: 2.5 io test regression? Diego Calleja García
2003-07-10  3:27 ` Nick Piggin [this message]
2003-07-10  7:13 ` Andrew Morton

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=3F0CDD3B.4080408@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --cc=diegocg@teleline.es \
    --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