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
If your k8s node has more cpus than your deployment limit, the golang scheduler will not be aware of the kubernetes CFS scheduler, leading to many/all coroutines in a sleep state, false result.
Setting GOMAXPROCS=2 as in k8s deployment can lead to better performance.
Thank you, @agravelot! I did some more research and even ran tests. You're right—GOMAXPROCS makes a significant difference! I'll be using it in all my future benchmarks.
If your k8s node has more cpus than your deployment limit, the golang scheduler will not be aware of the kubernetes CFS scheduler, leading to many/all coroutines in a sleep state, false result.
Setting
GOMAXPROCS=2
as in k8s deployment can lead to better performance.https://github.com/uber-go/automaxprocs is specially designed for this purpose.
Related discussion: #288
The text was updated successfully, but these errors were encountered: