linux-kernel - Re: [revert] mysql+oltp regression

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080811132902.GB14474@elte.hu>
Date:	Mon, 11 Aug 2008 15:29:02 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Gregory Haskins <ghaskins@...ell.com>
Cc:	Mike Galbraith <efault@....de>,
	LKML <linux-kernel@...r.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [revert] mysql+oltp regression


* Gregory Haskins <ghaskins@...ell.com> wrote:

>> ok, thanks. I'm curious, what are those ripple effects? Stability or 
>> performance?
>
> Performance.  I found it while working on my pi series (which fyi I 
> should have a v2 refresh for soon, probably today...i am hoping to get 
> some review feedback from you on that as well, time permitting of 
> course ;).
>
> Basically the behavior I was observing was that kernel builds via 
> distcc would cluster all the cc1 jobs on a single core.  At first I 
> thought my pi-series was screwed up, but then I realized I had applied 
> the patch referenced above earlier in my development tree, and 
> removing it allowed pi to work fine.
>
> I found the problem with in once boot cycle with ftrace (thanks 
> Steve!).  Basically newidle balancing was always returning "no 
> imbalance" even though I had 32 cc1 threads on 1 core, and 3 idle 
> cores.  Clearly not correct!  So I think that by adjusting the load 
> up, we throw off the hysteresis built into the load averages and cause 
> the system to incorrectly think it's balanced. TBD.

ok. If you touch that area i'd suggest to also test Mike's 
mysql+sysbench workload (all CPU bound, not IO bound) - it is rather 
sensitive to many aspects of load-balancing. Mysqld also has scalability 
limits due to user-space locking with increasing number of cores, so it 
will show wakeup and buddy balancing artifacts very quickly.

(With postgresql you'll need to go to 32 cores to see it scale badly 
under Linux due to user-space locking.)

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/