From: Anton Blanchard <anton@samba.org>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Brian Twichell <tbrian@us.ibm.com>,
David Lang <david.lang@digitalinsight.com>,
linux-kernel@vger.kernel.org, mbligh@mbligh.org,
slpratt@us.ibm.com
Subject: Re: Database regression due to scheduler changes ?
Date: Tue, 8 Nov 2005 12:15:47 +1100 [thread overview]
Message-ID: <20051108011547.GP12353@krispykreme> (raw)
In-Reply-To: <436FF6A6.1040708@yahoo.com.au>
Hi Nick,
> I would also take a look at removing SD_WAKE_IDLE from the flags.
> This flag should make balancing more aggressive, but it can have
> problems when applied to a NUMA domain due to too much task
> movement.
I was wondering how ppc64 ended up with different parameters in the NODE
definitions (added SD_BALANCE_NEWIDLE and SD_WAKE_IDLE) and it looks
like it was Andrew :)
http://lkml.org/lkml/2004/11/2/205
It looks like balancing was not agressive enough on his workload too.
Im a bit uneasy with only ppc64 having the two flags though.
Im also considering adding balance on fork for ppc64, it seems like a
lot of people like to run stream like benchmarks and Im getting tired of
telling them to lock their threads down to cpus.
Anton
next prev parent reply other threads:[~2005-11-08 1:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-07 22:17 Database regression due to scheduler changes ? Brian Twichell
2005-11-07 22:35 ` David Lang
2005-11-07 23:06 ` Brian Twichell
2005-11-08 0:51 ` Nick Piggin
2005-11-08 1:15 ` Anton Blanchard [this message]
2005-11-08 1:34 ` Martin J. Bligh
2005-11-08 1:46 ` Nick Piggin
2005-11-08 1:48 ` Nick Piggin
2005-11-08 1:58 ` Martin J. Bligh
2005-11-08 2:04 ` David Lang
2005-11-08 2:12 ` Martin J. Bligh
2005-11-08 2:15 ` Nick Piggin
2005-11-09 5:03 ` Brian Twichell
[not found] ` <43718DFE.3040600@yahoo.com.au>
2005-11-14 23:03 ` Brian Twichell
2005-11-08 2:31 ` Byron Stanoszek
2005-11-07 22:47 ` linux-os (Dick Johnson)
2005-11-08 3:54 ` Nick Piggin
[not found] <43715361.3070802@us.ibm.com>
2005-11-09 2:14 ` Andrew Theurer
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=20051108011547.GP12353@krispykreme \
--to=anton@samba.org \
--cc=david.lang@digitalinsight.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@mbligh.org \
--cc=nickpiggin@yahoo.com.au \
--cc=slpratt@us.ibm.com \
--cc=tbrian@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox