Messages in this thread | | | Date | Sun, 20 Jan 2013 23:52:20 +0800 | From | Alex Shi <> | Subject | Re: sched: Consequences of integrating the Per Entity Load Tracking Metric into the Load Balancer |
| |
>>> The blocked load of a cluster will be high if the blocked tasks have >>> run recently. The contribution of a blocked task will be divided by 2 >>> each 32ms, so it means that a high blocked load will be made of recent >>> running tasks and the long sleeping tasks will not influence the load >>> balancing. >>> The load balance period is between 1 tick (10ms for idle load balance >>> on ARM) and up to 256 ms (for busy load balance) so a high blocked >>> load should imply some tasks that have run recently otherwise your >>> blocked load will be small and will not have a large influence on your >>> load balance > > Just tried using cfs's runnable_load_avg + blocked_load_avg in > weighted_cpuload() with my v3 patchset, aim9 shared workfile testing > show the performance dropped 70% more on the NHM EP machine. :( >
Ops, the performance is still worse than just count runnable_load_avg. But dropping is not so big, it dropped 30%, not 70%.
-- Thanks Alex
| |