You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rusty implements load balancer based on load sums where a task's load is defined as its weight * duty cycle. Nice level 0 maps to the default weight 100 and float 1.0, so a nice-0 thread which is constantly runnable has the load of 1.0. The following is from scx_rusty --stats 1 on a Ryzen 3900x (four CCXs with 3 cores / 6 threads on each CCX, totaling 24 CPUs) with stress -c 23 as the workload:
As stress -c 23 creates 23 full duty cycle threads of the default weight, the load sum should be around 23 and it checks out. However, the following is the output with stress -c 25 on the same setup:
Something goes really wrong and the load sum ends up more than two orders of magnitude larger than what it should be. Subsequently, load balancing itself seems broken too. The following is the output from first running stress -c 24 and then taskset 0x7007 stress -c 24. The load balancer should be moving the load from the first command away from DOM0 to balance it out but it doesn't do anything:
rusty implements load balancer based on load sums where a task's load is defined as its
weight * duty cycle
. Nice level 0 maps to the default weight 100 and float 1.0, so a nice-0 thread which is constantly runnable has the load of 1.0. The following is fromscx_rusty --stats 1
on a Ryzen 3900x (four CCXs with 3 cores / 6 threads on each CCX, totaling 24 CPUs) withstress -c 23
as the workload:As
stress -c 23
creates 23 full duty cycle threads of the default weight, the load sum should be around 23 and it checks out. However, the following is the output withstress -c 25
on the same setup:Something goes really wrong and the load sum ends up more than two orders of magnitude larger than what it should be. Subsequently, load balancing itself seems broken too. The following is the output from first running
stress -c 24
and thentaskset 0x7007 stress -c 24
. The load balancer should be moving the load from the first command away from DOM0 to balance it out but it doesn't do anything:The text was updated successfully, but these errors were encountered: