From: Dave Olien <dmo@osdl.org>
To: cliff white <cliffw@osdl.org>
Cc: Nick Piggin <piggin@cyberone.com.au>,
mhf@linuxmail.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test8/test9 io scheduler needs tuning?
Date: Tue, 28 Oct 2003 13:18:44 -0800 [thread overview]
Message-ID: <20031028211844.GA8285@osdl.org> (raw)
In-Reply-To: <20031028092612.68d1c80d.cliffw@osdl.org>
Yes, it seems Nick's latest patch from 10/27, has helped reaim
considerably.
The dbt2 workload still has a problem though. Mary ran this patch today,
with deadline and with as-iosched:
2.6.0-test9, elevator=deadline 1644 NOTPM
2.6.0-test9, unpatched as-iosched 977 NOTPM
2.6.0-test9, as-iosched with as-fix.patch 980 NOTPM
Higher NOTPM numbers are better.
On Tue, Oct 28, 2003 at 09:26:12AM -0800, cliff white wrote:
> > cliff white wrote:
>
> So far, looks quite good. ( i know 2.4.18 is wierd for some, but they were
> hot off the stp, so i used 'em )
>
> 4-cpu
> STP id Kernel Name MaxJPM Change Options
> 282391 linux-2.4.18 5250.23 0.00
> 282413 Nick's patch 5484.95 4.27 elevator=deadline
> 282413 Nick's patch 5416.51 3.06
>
> 282395 linux-2.4.18 6581.17 0.0
> 282415 Nick's patch 8293.95 20.6
> 282415 Nick's patch 8484.95 22.43 elevator=deadline
>
> And, the graph is nice and flat!
> http://khack.osdl.org/stp/282416/results/jpm.png
>
> Full results: http://developer.osdl.org/cliffw/reaim/index.html
>
> Any test detail: http://khack.osdl.org/stp/<STP id>
>
> cliffw
>
> >
>
>
> --
> The church is near, but the road is icy.
> The bar is far, but i will walk carefully. - Russian proverb
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2003-10-28 21:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 21:52 2.6.0-test8/test9 io scheduler needs tuning? Michael Frank
2003-10-27 22:55 ` cliff white
2003-10-27 23:50 ` Nick Piggin
2003-10-28 1:37 ` Nigel Cunningham
2003-10-28 1:48 ` Nick Piggin
2003-10-28 2:58 ` Michael Frank
2003-10-28 2:57 ` Michael Frank
2003-10-28 3:31 ` Nigel Cunningham
2003-10-28 3:54 ` Nick Piggin
2003-10-28 7:48 ` Michael Frank
2003-10-28 4:13 ` Michael Frank
2003-10-28 4:30 ` Nick Piggin
2003-10-28 6:11 ` Michael Frank
2003-10-28 17:42 ` Martin Josefsson
2003-10-28 17:26 ` cliff white
2003-10-28 21:18 ` Dave Olien [this message]
2003-10-29 2:40 ` Nick Piggin
2003-10-29 4:56 ` Michael Frank
2003-10-29 16:47 ` Michael Frank
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=20031028211844.GA8285@osdl.org \
--to=dmo@osdl.org \
--cc=cliffw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhf@linuxmail.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