Skip to contentSkip to conversation

better wake-balancing, #2

PATCH Chuck Ebbert 3 participants 3 messages Jul 30, 2005 – Jul 31, 2005

lore
Share & tools
lore
#0 lore raw
Quoted 4 lines · Ingo Molnar

do wakeup-balancing only if the wakeup-CPU is idle.

this prevents excessive wakeup-balancing while the system is highly loaded, but helps spread out the workload on partly idle systems.

I tested this with Volanomark on dual-processor PII Xeon -- the results were very bad:

Before: 5863 messages per second

124169 schedule 64.1369
64663 _spin_unlock_irqrestore 4041.4375
7949 tcp_clean_rtx_queue 6.5370
6787 net_rx_action 24.9522

After: 5569 messages per second

139417 schedule 72.0129
82169 _spin_unlock_irqrestore 5135.5625
9949 tcp_clean_rtx_queue 8.1817
7917 net_rx_action 29.1066

__
Chuck

#1 lore raw
Quoted 6 lines · Chuck Ebbert
Quoted 4 lines · Ingo Molnar

do wakeup-balancing only if the wakeup-CPU is idle.

this prevents excessive wakeup-balancing while the system is highly loaded, but helps spread out the workload on partly idle systems.

Quoted 6 lines

I tested this with Volanomark on dual-processor PII Xeon -- the results were very bad:

Before: 5863 messages per second

After: 5569 messages per second

Can you check schedstats or otherwise to find if volanomark uses sched_yield() ? When last this benchmark came up, it appeared that no jvm used futexes and left locking to yielding. We really should find out if that is the case before trying to optimise for this benchmark.

Cheers,
Con

#2 lore raw
In reply to Chuck Ebbert
Quoted 9 lines · Chuck Ebbert
Quoted 4 lines · Ingo Molnar

do wakeup-balancing only if the wakeup-CPU is idle.

this prevents excessive wakeup-balancing while the system is highly loaded, but helps spread out the workload on partly idle systems.

I tested this with Volanomark on dual-processor PII Xeon -- the results were very bad:

which patch have you tested? The mail you replied to above is for patch #2, while on SMT/HT boxes it's patch #3 that is the correct approach.

furthermore, which base kernel have you applied the patch to? Best would be to test the following kernels:

2.6.13-rc4 + sched-rollup
2.6.13-rc4 + sched-rollup + better-wake-balance-#3

the sched-rollup and the latest better-wake-balance patches can be found at:

http://redhat.com/~mingo/scheduler-patches/

(sched-rollup is the current scheduler patch-queue in -mm. And if you have time, it would also be nice to have a 2.6.13-rc4 baseline for VolanoMark, and perhaps a 2.6.12 measurement too, so that we can see how things changed.)

Ingo