public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@digeo.com>
Subject: Re: [BENCHMARK] 2.5.63-mm2 + i/o schedulers with contest
Date: Tue, 04 Mar 2003 15:18:58 +1100	[thread overview]
Message-ID: <3E642932.7070205@cyberone.com.au> (raw)
In-Reply-To: <200303041354.03428.kernel@kolivas.org>

Con Kolivas wrote:

>Here are contest (http://contest.kolivas.org) benchmarks using the osdl 
>hardware (http://www.osdl.org) for 2.5.63-mm2 and various i/o schedulers:
>
Thanks :)

>It seems the AS scheduler reliably takes slightly longer to compile the kernel 
>in no load conditions, but only about 1% cpu.
>
It is likely that AS will wait too long for gcc to submit another
read and end up timing out anyway. Hopefully IO history tracking
will fix this up - for some loads the effect can be much worse.

>
>
>CFQ and DL faster to compile the kernel than AS while extracting or creating 
>tars.
>
This is likely to be balancing differences from LCPU% it does
seem like AS is doing a bit more "load" work.

>
>
>AS significantly faster under writing large file to the same disk (io_load) or 
>other disk (io_other) conditions. The CFQ and DL schedulers showed much more 
>variability on io_load during testing but did not drop below 140 seconds.
>
small randomish reads vs large writes _is_ where AS really can
perform better than non a non AS scheduler. Unfortunately gcc
doesn't have the _best_ IO pattern for AS ;)

>
>
>CFQ and DL scheduler were faster compiling the kernel under read_load,  
>list_load and dbench_load.
>
>Mem_load result of AS being slower was just plain weird with the result rising 
>from 100 to 150 during testing.
>
I would like to see if AS helps much with a swap/memory
thrashing load.


  reply	other threads:[~2003-03-04  4:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-04  2:54 [BENCHMARK] 2.5.63-mm2 + i/o schedulers with contest Con Kolivas
2003-03-04  4:18 ` Nick Piggin [this message]
2003-03-04  5:15   ` Con Kolivas
2003-03-04  5:26     ` Nick Piggin
2003-03-04  5:29       ` Con Kolivas
2003-03-04  8:10 ` Andrew Morton
2003-03-04  8:20   ` Con Kolivas
2003-03-05  6:02   ` 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=3E642932.7070205@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --cc=akpm@digeo.com \
    --cc=kernel@kolivas.org \
    --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