Re:Erlang Garbage Collector
by weberc2 on Thursday November 30, 2017 @11:45PM
(#15821980)
Really? I've never heard anyone mention this and I've followed Go for years.
[ Parent
| on HN ]
Yeah, it mostly happens when you have a server which runs an abnormally large task or payload, causes the heap to grow, and does it in a way that Go can't release the memory back to the OS due to heap fragmentation.
I haven't looked at this for a while but I believe it's still an issue.
https://github.com/cockroachdb/cockroach/issues/2007 https://github.com/golang/go/issues/18896 https://github.com/golang/go/issues/14045