From: Nick Piggin <piggin@cyberone.com.au>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Nick's scheduler policy v10
Date: Tue, 02 Sep 2003 18:04:33 +1000 [thread overview]
Message-ID: <3F544F11.4010700@cyberone.com.au> (raw)
In-Reply-To: <6860000.1062441073@[10.10.2.4]>
Martin J. Bligh wrote:
>>>>Kernbench: (make -j vmlinux, maximal tasks)
>>>> Elapsed System User CPU
>>>> 2.6.0-test4 45.87 116.92 571.10 1499.00
>>>> 2.6.0-test4-nick10 46.91 114.03 584.16 1489.25
>>>>
>>>>
>>>Actually, now looks like you have significantly more idle time, so perhaps
>>>the cross-cpu (or cross-node) balancing isn't agressive enough:
>>>
>>>
>>Yeah, there is a patch for this in mm that is not in mine. It should
>>help both mine and mainline though...
>>
>
>Not convinced of that - mm performs worse than mainline for me.
>
Well, one of Con's patches caused a lot of idle time on volanomark.
The reason for the change was unclear. I guess either a fairness or
wakeup latency change (yes, it was a very scientific process, ahem).
Anyway, in the process of looking at the load balancing, we found
and fixed a problem (although it might now possibly over balance).
This did cure most of the idle problems.
So it could just be small changes causing things to go out of whack.
I will try to get better data after (if ever) the thing is working
nicely on the desktop.
next prev parent reply other threads:[~2003-09-02 8:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-30 6:31 [PATCH] Nick's scheduler policy v10 Nick Piggin
2003-08-31 20:20 ` Martin J. Bligh
2003-08-31 20:41 ` Martin J. Bligh
2003-09-01 1:47 ` Nick Piggin
2003-09-01 18:31 ` Martin J. Bligh
2003-09-02 8:04 ` Nick Piggin [this message]
2003-09-02 14:57 ` Martin J. Bligh
2003-09-02 23:50 ` Nick Piggin
2003-09-03 1:55 ` Con Kolivas
2003-09-01 1:44 ` Nick Piggin
2003-09-04 22:55 ` bill davidsen
2003-09-04 23:27 ` Mike Fedyk
2003-09-05 3:41 ` Bill Davidsen
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=3F544F11.4010700@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
/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.