From: Roger Luethi <rl@hellgate.ch>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [CFT][PATCH] new scheduler policy
Date: Fri, 22 Aug 2003 10:55:08 +0200 [thread overview]
Message-ID: <20030822085508.GA10215@k3.hellgate.ch> (raw)
In-Reply-To: <3F4182FD.3040900@cyberone.com.au>
On Tue, 19 Aug 2003 11:53:01 +1000, Nick Piggin wrote:
> I haven't run many tests on it - my mind blanked when I tried to
> remember the scores of scheduler "exploits" thrown around. So if
> anyone would like to suggest some, or better still, run some,
> please do so. And be nice, this isn't my type of scheduler :P
I timed a pathological benchmark from hell I've been playing with lately.
Three consecutive runs following a fresh boot. Time is in seconds:
2.4.21 821 21 25
2.6.0-test3-mm1 724 946 896
2.6.0-test3-mm1-nick 905 987 997
Runtime with ideal scheduling: < 2 seconds (we're thrashing).
If anybody has thrashing test cases closer to the real world, I'd be very
interested to learn about them.
Roger
next prev parent reply other threads:[~2003-08-22 8:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-19 1:53 [CFT][PATCH] new scheduler policy Nick Piggin
2003-08-19 2:35 ` William Lee Irwin III
2003-08-19 2:46 ` Nick Piggin
2003-08-19 2:59 ` Nick Piggin
2003-08-19 5:15 ` Matt Mackall
2003-08-19 5:34 ` Nick Piggin
2003-08-19 5:45 ` Matt Mackall
2003-08-19 10:24 ` Mike Galbraith
2003-08-19 13:40 ` Nick Piggin
2003-08-19 18:49 ` Mike Galbraith
2003-08-20 2:13 ` William Lee Irwin III
2003-08-25 13:47 ` Haoqiang Zheng
2003-08-25 14:03 ` Nick Piggin
2003-08-25 15:11 ` Haoqiang Zheng
2003-09-02 14:25 ` Pavel Machek
2003-09-08 13:40 ` Alan Cox
2003-09-08 14:20 ` Haoqiang Zheng
2003-09-08 14:28 ` Alan Cox
2003-09-08 15:10 ` Haoqiang Zheng
2003-08-22 8:55 ` Roger Luethi [this message]
2003-08-22 13:08 ` Nick Piggin
2003-08-22 15:11 ` Roger Luethi
2003-08-23 0:22 ` Nick Piggin
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=20030822085508.GA10215@k3.hellgate.ch \
--to=rl@hellgate.ch \
--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 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.