Messages in this thread | | | Subject | Re: 20% performance drop on PostgreSQL 9.2 from kernel 3.5.3 to 3.6-rc5 on AMD chipsets - bisected | From | Mike Galbraith <> | Date | Wed, 26 Sep 2012 04:00:45 +0200 |
| |
On Tue, 2012-09-25 at 10:21 -0700, Linus Torvalds wrote: > On Tue, Sep 25, 2012 at 10:00 AM, Borislav Petkov <bp@alien8.de> wrote: > > > > 3.6-rc6+tip/auto-latest-kill select_idle_sibling() > > Is this literally just removing it entirely? Because apart from the > latency spike at 4 procs (and the latency numbers look very noisy, so > that's probably just noise), it looks clearly superior to everything > else. On that benchmark, at least.
Yes. On AMD, the best thing you can do for fast switchers AFAIKT is turn it off. Different story on Intel.
> How does pgbench look? That's the one that apparently really wants to > spread out, possibly due to user-level spinlocks. So I assume it will > show the reverse pattern, with "kill select_idle_sibling" being the > worst case. Sad, because it really would be lovely to just remove that > thing ;)
It _is_ irritating. There's nohz, governors, and then come radically different cross cpu data blasting ability on top. On Intel, it wins at the same fast movers it demolishes on AMD. Throttle it, and that goes away, along with some other issues.
Or just kill it, then integrate what it does for you into a smarter lighter wakeup balance.. but then that has to climb that same hills.
-Mike
| |