I really hope this doesn&#x27;t become a meme.<p>Pause time is only one metric that&#x27;s relevant when looking at GC, another very important one is throughput.<p>In fact you can get very low (10-50 msec) pause times with the latest JVMs even with very large heaps, you can just request it at the command line, but you&#x27;ll pay for it with slower execution. There is always a tradeoff. Go doesn&#x27;t have anything fundamentally new in this field.<p>There is a report here on an adapted HotSpot (not integrated into the mainline JVM though) that gives &lt;10msec pause times at the 99th percentile and an 8 gigabyte heap:<p><pre><code>   http:&#x2F;&#x2F;welf.se&#x2F;files&#x2F;OL15.pdf
</code></pre>
But you pay for it with a 15% CPU overhead.<p>Go&#x27;s GC seems to actually do a full concurrent mark&#x2F;sweep of the entire heap every single time. That suggests to me that throughput could be rather poor.