Go is not cgroup aware. This means that Scrutiny will be throttled hard in containerised environments with CPU limits.
The below screenshot shows the container with a CPU limit in Kubernetes. The first half of the time series is on a 13600k, with 20 threads. The second half is when the machine changed to use an EPYC 7763 with 128 threads.
Expected behavior
Scrutiny should not be CPU throttling with adequate resources, and the throttling should not scale with the number of available threads.
Describe the bug
Go is not cgroup aware. This means that Scrutiny will be throttled hard in containerised environments with CPU limits.
The below screenshot shows the container with a CPU limit in Kubernetes. The first half of the time series is on a 13600k, with 20 threads. The second half is when the machine changed to use an EPYC 7763 with 128 threads.
Expected behavior
Scrutiny should not be CPU throttling with adequate resources, and the throttling should not scale with the number of available threads.
automaxprocs can use cgroups automatically.
Screenshots
See above.
Log Files
N/A