We recently had the problem, that the go garbage collector ran hot on a kubernetes pod and we didn’t find out why. Specs were as follows:
- heap size as reported by the GC was roughly 3GB - GOGC percentage was at 100 - GOMEMLIMIT was set to something way above current heap size (6750MiB). - kubernetes memory limit was at 9GB - kubernetes memory request was at 6GB These things all looked good for me. We found out that the problem was fixed by setting the memory request from 6 to 9GB. And here comes the question: How does the GO GC even know about the requested memory? I haven't found anything in the docs or via Google. Could someone point us to the section in code? It is nice that this behavior prevents avoidable OOMs, but it also puzzled us for a while. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/golang-nuts/de1d85a6-5ae7-4784-bd7b-e9decc6834b3n%40googlegroups.com.
