From: Mike Galbraith <efault@gmx.de>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: lkml <linux-kernel@vger.kernel.org>,
Suresh Siddha <suresh.b.siddha@intel.com>,
Paul Turner <pjt@google.com>,
Arjan Van De Ven <arjan@linux.intel.com>
Subject: Re: [rfc][patch] select_idle_sibling() inducing bouncing on westmere
Date: Wed, 06 Jun 2012 12:38:59 +0200 [thread overview]
Message-ID: <1338979139.28497.44.camel@marge.simpson.net> (raw)
In-Reply-To: <1338977861.28497.36.camel@marge.simpson.net>
btw, numbers are intended to invoke: "Gee, wonder what if anything this
does to/for my favorite load" ;-)
On Wed, 2012-06-06 at 12:17 +0200, Mike Galbraith wrote:
> On Thu, 2012-05-24 at 15:17 +0200, Peter Zijlstra wrote:
>
> > Did you do you numbers with the distro NR_CPUS=4096 bloat?
>
> 4 socket Westmere-EX 40 core box.. ouch^ouch.
>
> 3.0 has none of the below, 3.0x all, 3.0xx all but the ones commented
> out. Most of the deltas are sibling avoidance, though throttle-nohz
> plays a role in 3.0 vs 3.0x, as does knob tweakery, though very very
> small for these particular tests. The rest are ~meaningless.
>
> sched-use-rt-nr_cpus_allowed-to-recover-select_task_rq-cycles.patch
> sched-set-skip_clock_update-when-yielding.patch
> sched-throttle-nohz.patch
> sched-Wrap-scheduler-p--cpus_allowed-access.patch
> sched-Avoid-SMT-siblings-in-select_idle_sibling-if-possible.patch
> sched-Clean-up-domain-traversal-in-select_idle_sibling.patch
> sched-Remove-rcu_read_lock-unlock-from-select_idle_sibling.patch
> sched-Fix-the-sched-group-node-allocation-for-SD_OVERLAP-domains.patch
> sched-domain-flags-proc-handler.patch
> # sched-tweak-select_idle_sibling.patch
> sched-tweak-knobs.patch
> # sched-ratelimit-affine-wakeup-migrations.patch
>
> thench 1 2 4 8 16 32 64 128
> 3.0 225 451 911 1573 2723 3501 11189 13951
> 3.0x 299 603 1211 2418 4697 6847 11606 14557
> vs 3.0 1.328 1.337 1.329 1.537 1.724 1.955 1.037 1.043
>
> 3.0xx 30 41 118 645 3769 6214 12233 14312
> vs 3.0x 0.100 0.067 0.097 0.266 0.802 0.907 1.054 0.983
> hmmm
> aim7 ~low load.. not saturating.
>
> Benchmark Version Machine Run Date
> AIM Multiuser Benchmark - Suite VII "1.1" 3.0x Jun 6 09:29:20 2012
>
> Tasks Jobs/Min JTI Real CPU Jobs/sec/task
> 64 26223.1 98 14.8 293.3 6.8289
>
> Benchmark Version Machine Run Date
> AIM Multiuser Benchmark - Suite VII "1.1" 3.0xx Jun 6 11:12:21 2012
>
> Tasks Jobs/Min JTI Real CPU Jobs/sec/task
> 64 18845.5 82 20.6 254.8 4.9077 vs 3.0x 0.718
>
>
prev parent reply other threads:[~2012-06-06 10:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 11:04 Mike Galbraith
2012-05-24 13:17 ` Peter Zijlstra
2012-05-24 13:20 ` Peter Zijlstra
2012-05-25 6:14 ` Mike Galbraith
2012-05-26 6:37 ` Mike Galbraith
2012-05-26 7:29 ` Peter Zijlstra
2012-05-26 8:27 ` Mike Galbraith
2012-05-27 9:17 ` Mike Galbraith
2012-05-27 11:02 ` Mike Galbraith
2012-05-27 11:12 ` Mike Galbraith
2012-05-27 14:11 ` Arjan van de Ven
2012-05-27 14:29 ` Mike Galbraith
2012-05-27 14:32 ` Mike Galbraith
2012-05-29 18:58 ` Andreas Herrmann
2012-05-25 6:08 ` Mike Galbraith
2012-05-25 8:06 ` Mike Galbraith
2012-06-05 14:30 ` Mike Galbraith
2012-06-11 16:57 ` [patch v3] sched: fix select_idle_sibling() induced bouncing Mike Galbraith
2012-06-11 17:22 ` Peter Zijlstra
2012-06-11 17:55 ` Mike Galbraith
2012-06-11 18:53 ` Suresh Siddha
2012-06-12 3:18 ` Mike Galbraith
2012-06-20 10:48 ` [tip:sched/core] sched: Improve scalability via 'CPU buddies', which withstand random perturbations tip-bot for Mike Galbraith
2012-07-24 14:18 ` tip-bot for Mike Galbraith
2012-06-19 8:47 ` [patch v3] sched: fix select_idle_sibling() induced bouncing Paul Turner
2012-06-06 10:17 ` [rfc][patch] select_idle_sibling() inducing bouncing on westmere Mike Galbraith
2012-06-06 10:38 ` Mike Galbraith [this message]
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=1338979139.28497.44.camel@marge.simpson.net \
--to=efault@gmx.de \
--cc=a.p.zijlstra@chello.nl \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pjt@google.com \
--cc=suresh.b.siddha@intel.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
Powered by JetHome