<p>Has anybody seen some benchmarks of Go 1.6 comparing to 1.5? </p>
<hr/>**评论：**<br/><br/>vmihailenco: <pre><p><a href="https://groups.google.com/forum/#!topic/golang-dev/fx3lxHq-9xc">https://groups.google.com/forum/#!topic/golang-dev/fx3lxHq-9xc</a></p></pre>throwaway19235402: <pre><p>Thanks, not exactly what they were promising for 1.6.</p></pre>bradfitz: <pre><p>Also looks like the GC folk haven't replied. Maybe it's a bug.</p></pre>throwaway19235402: <pre><p>Let's hope so!</p></pre>mekanikal_keyboard: <pre><p>i hope so, as much as i want to play with http2, i don't think it is worth it to ship a release that degrades like that</p></pre>f2f: <pre><p><a href="http://www.infoq.com/presentations/go-gc-performance" rel="nofollow">http://www.infoq.com/presentations/go-gc-performance</a></p>
<p>see the slide around the 27 minute mark.</p></pre>throwaway19235402: <pre><p>Interesting, this looks good. Now, we have two contrasting results.</p></pre>twelph: <pre><p>I'm not in the loop completely about how the compiler is functioning lately, are we still trying to recover the speed performance that went down when the go compiler code was autoconverted from C? </p></pre>throwaway19235402: <pre><p>That conversion happened in 1.5 so yes 1.6 is supposed to fix that.</p></pre>Little_Johnny: <pre><p>If you are referring to Compiler performance, it has not improved for Go1.6 significantly from what I have seen.</p></pre>throwaway19235402: <pre><p>Well, any kind of performance. So compiler performance definitely as well as it degraded quite much in 1.5.</p></pre>
