From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: 'Ingo Molnar' <mingo@elte.hu>, Nick Piggin <nickpiggin@yahoo.com.au>
Cc: linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
Andrew Morton <akpm@osdl.org>, John Hawkes <hawkes@sgi.com>,
"Martin J. Bligh" <mbligh@mbligh.org>, Paul Jackson <pj@sgi.com>
Subject: RE: [sched, patch] better wake-balancing, #3
Date: Mon, 08 Aug 2005 23:18:42 +0000 [thread overview]
Message-ID: <200508082318.j78NIlg21385@unix-os.sc.intel.com> (raw)
In-Reply-To: <20050730071917.GA31822@elte.hu>
In-Reply-To: <20050729162108.GA10243@elte.hu>
Ingo Molnar wrote on Saturday, July 30, 2005 12:19 AM
> * Nick Piggin <nickpiggin@yahoo.com.au> wrote:
>
> > > here's an updated patch. It handles one more detail: on SCHED_SMT we
> > > should check the idleness of siblings too. Benchmark numbers still
> > > look good.
> >
> > Maybe. Ken hasn't measured the effect of wake balancing in 2.6.13,
> > which is quite a lot different to that found in 2.6.12.
> >
> > I don't really like having a hard cutoff like that -wake balancing can
> > be important for IO workloads, though I haven't measured for a long
> > time. [...]
>
> well, i have measured it, and it was a win for just about everything
> that is not idle, and even for an IPC (SysV semaphores) half-idle
> workload i've measured a 3% gain. No performance loss in tbench either,
> which is clearly the most sensitive to affine/passive balancing. But i'd
> like to see what Ken's (and others') numbers are.
>
> the hard cutoff also has the benefit that it allows us to potentially
> make wakeup migration _more_ agressive in the future. So instead of
> having to think about weakening it due to the tradeoffs present in e.g.
> Ken's workload, we can actually make it stronger.
Sorry it took us a while to get the experiment done on our large db setup.
This patch has the same effectiveness compare to turning off both
SD_WAKE_BALANCE and SD_WAKE_AFFINE, (+2.2% on db OLTP workload). We like
it a lot.
- Ken
next prev parent reply other threads:[~2005-08-08 23:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 23:08 Delete scheduler SD_WAKE_AFFINE and SD_WAKE_BALANCE flags Chen, Kenneth W
2005-07-28 23:34 ` Nick Piggin
2005-07-28 23:48 ` Chen, Kenneth W
2005-07-29 1:25 ` Nick Piggin
2005-07-29 1:39 ` Chen, Kenneth W
2005-07-29 1:46 ` Nick Piggin
2005-07-29 1:53 ` Chen, Kenneth W
2005-07-29 2:01 ` Nick Piggin
2005-07-29 6:27 ` Chen, Kenneth W
2005-07-29 8:48 ` Nick Piggin
2005-07-29 8:53 ` Ingo Molnar
2005-07-29 8:59 ` Nick Piggin
2005-07-29 9:01 ` Ingo Molnar
2005-07-29 9:07 ` Ingo Molnar
2005-07-29 16:40 ` Ingo Molnar
2005-07-29 11:48 ` [patch] remove wake-balancing Ingo Molnar
2005-07-29 14:13 ` [sched, patch] better wake-balancing Ingo Molnar
2005-07-29 15:02 ` [sched, patch] better wake-balancing, #2 Ingo Molnar
2005-07-29 16:21 ` [sched, patch] better wake-balancing, #3 Ingo Molnar
2005-07-30 0:08 ` Nick Piggin
2005-07-30 7:19 ` Ingo Molnar
2005-07-31 1:15 ` Nick Piggin
2005-08-01 17:13 ` Siddha, Suresh B
2005-08-08 23:18 ` Chen, Kenneth W [this message]
2005-07-30 23:26 ` [sched, patch] better wake-balancing, #2 Chuck Ebbert
2005-07-31 4:35 ` Con Kolivas
2005-07-31 6:29 ` Ingo Molnar
2005-07-31 13:35 ` Chuck Ebbert
2005-07-29 11:26 ` Delete scheduler SD_WAKE_AFFINE and SD_WAKE_BALANCE flags Ingo Molnar
2005-07-29 17:30 ` Chen, Kenneth W
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=200508082318.j78NIlg21385@unix-os.sc.intel.com \
--to=kenneth.w.chen@intel.com \
--cc=akpm@osdl.org \
--cc=hawkes@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@mbligh.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=pj@sgi.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