Because the .26 group scheduler wasn't SMP aware. The extra cost comes
from the fact that .27 is.--
What you can do it increase the /proc/sys/kernel/sched_shares_ratelimit
value and thereby decrease the accuracy of the SMP fairness of the group
scheduler.--
Peter,
We increased sched_shares_ratelimit and were able to recover the 2% performance regression.
Thanks,-----Original Message-----
From: Peter Zijlstra [mailto:peterz@infradead.org]
Sent: Monday, September 08, 2008 11:04 AM
To: Ma, Chinang
Cc: Ingo Molnar; Srivatsa Vaddagiri; Mike Galbraith; Gregory Haskins; Steven Rostedt; Nick Piggin; Siddha, Suresh B; Wilcox, Matthew R; Tripathi, Sharad C; Chilukuri, Harita; linux-kernel@vger.kernel.org
Subject: Re: 2.6.27-rc5 OLTP performance regressionWhat you can do it increase the /proc/sys/kernel/sched_shares_ratelimit
value and thereby decrease the accuracy of the SMP fairness of the group
scheduler.--
great. Could you please post a patch for that?
Ingo
--
I increased the /proc/sys/kernel/sched_shares_ratelimit from 1 millisecond to one second to reduce the frequency of shares update. That was okay for OLTP workload. As Peter mentioned, a larger value will reduce the accuracy of SMP fairness for group scheduler and the ratelimit and using a larger default value may not be good for general case.
Thanks,
Chinang
-----Original Message-----
From: Ingo Molnar [mailto:mingo@elte.hu]
Sent: Wednesday, September 10, 2008 5:26 AM
To: Ma, Chinang
Cc: Peter Zijlstra; Srivatsa Vaddagiri; Mike Galbraith; Gregory Haskins; Steven Rostedt; Nick Piggin; Siddha, Suresh B; Wilcox, Matthew R; Tripathi, Sharad C; Chilukuri, Harita; linux-kernel@vger.kernel.org
Subject: Re: 2.6.27-rc5 OLTP performance regressiongreat. Could you please post a patch for that?
Ingo
--
does 10 msecs already get you most of the 2%? 1000 millisecond sounds
very (and probably unacceptable) coarse.Ingo
--
When set to 10 ms the regression is about 0.4%. We get most of the 2%.
Chinang
-----Original Message-----
From: Ingo Molnar [mailto:mingo@elte.hu]
Sent: Wednesday, September 10, 2008 10:35 AM
To: Ma, Chinang
Cc: Peter Zijlstra; Srivatsa Vaddagiri; Mike Galbraith; Gregory Haskins; Steven Rostedt; Nick Piggin; Siddha, Suresh B; Wilcox, Matthew R; Tripathi, Sharad C; Chilukuri, Harita; linux-kernel@vger.kernel.org
Subject: Re: 2.6.27-rc5 OLTP performance regressiondoes 10 msecs already get you most of the 2%? 1000 millisecond sounds
very (and probably unacceptable) coarse.Ingo
--
| Parag Warudkar | BUG: soft lockup - CPU#1 stuck for 15s! [swapper:0] |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 010/196] Chinese: add translation of Codingstyle |
| Andrew Morton | -mm merge plans for 2.6.23 |
git: | |
| Gerrit Renker | [PATCH 24/37] dccp: Processing Confirm options |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Alexey Dobriyan | Re: [GIT]: Networking |
| david | Re: iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49 |
