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
We use this as a library in an application of ours, but we have found that the process never uses more than 1 CPU and will start to throttle new connections when the app gets close to using 1 CPU.
Any help configuring the app to use more than a single CPU appreciated.
The text was updated successfully, but these errors were encountered:
Hello, there are no CPU restrictions and it does not throttle. All
scheduling is done by the Go runtime.
Most likely, it sounds like your storage is slow and cannot keep up. To
confirm, you can use the iostat command and check the await column
See https://coderwall.com/p/utc42q/understanding-iostat
On Tue, 9 Mar 2021 at 01:22, cten ***@***.***> wrote:
We use this as a library in an application of ours, but we have found that
the process never uses more than 1 CPU and will start to throttle new
connections when the app gets close to using 1 CPU.
Any help configuring the app to use more than a single CPU appreciated.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#226>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAE6MP6GT6C35P4H5FBY7TDTCT2V3ANCNFSM4YZWBY3A>
.
We use this as a library in an application of ours, but we have found that the process never uses more than 1 CPU and will start to throttle new connections when the app gets close to using 1 CPU.
Any help configuring the app to use more than a single CPU appreciated.
The text was updated successfully, but these errors were encountered: