Hacker News Reader

Did Go ever fix that problem where short term high memory usage can cause large empty heaps because of the lack of compaction?

I remember a rash of articles about this phenomena a while back. This article seems to think its not an issue so I'm wondering when it was fixed.

View on HN

No, it was never fixed and probably never will be, because it would make Go perform worse in the latency-sensitive microbenchmarks it wants to do well in.

that was never an issue? maybe your thinking of the slowness golang had in returning memory to the OS? that was resolved.

Reply on news.ycombinator.com