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
I'm not sure this report is actionable. If you are running on a low-memory machine and you allocate a lot, it's unavoidable that the GC will consume a fair amount of CPU, since it has a lot of work to do.
The only way to fix this is to change your program to allocate less. This will lower the CPU load (at least the part of it the GC is responsible of).
Another solution would be to decrease GOGC (e.g. you could set GOGC=50), that would lower the GC's cpu usage, but it'll increase the used memory, so you likely cannot afford to do this on a low-memory machine.
Also the garbage collector has improved since 1.10. The current release is 1.13.
The garbage collector team is always happy to get test cases they can use to test the garbage collector. But without a lot more information, there is nothing we can do here.
go 1.10.1
Frequent GC caused by insufficient memory in the host results in high cpu load
The text was updated successfully, but these errors were encountered: