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
When running Burrow on Kubernetes, we see a lot of CPU throttling during the initial startup. This happens because of the CPU limit we set on the container.
Two way to fix this:
manually setting GOMAXPROCS environment variable to match the CPU limit
Unfortunately, Burrow force GOMAXPROCS to be equal to the number of CPU cores main.go#L71 (which in a container, is equal to the number of CPU cores of the host, not the container), so I can't set GOMAXPROCS manually.
Would you consider a PR that use automaxprocs?
Or at minimum a PR that add a configuration to disable main.go#L71?
The text was updated successfully, but these errors were encountered:
When running Burrow on Kubernetes, we see a lot of CPU throttling during the initial startup. This happens because of the CPU limit we set on the container.
Two way to fix this:
GOMAXPROCS
environment variable to match the CPU limitUnfortunately, Burrow force GOMAXPROCS to be equal to the number of CPU cores main.go#L71 (which in a container, is equal to the number of CPU cores of the host, not the container), so I can't set
GOMAXPROCS
manually.The text was updated successfully, but these errors were encountered: