News for hackers. Stuff that matters.

A comment on How Go improves expressiveness without sacrificing performance.

Re:How Go improves expressiveness without sacrificing perfor... by thebigshane on Sunday February 12, 2012 @12:47AM (#3581210)
Can anyone explain why BenchmarkUnroll was specifically set to run twice as many iterations as the other two for the timing tests? It seems intentional. But why? Is there some overhead in having the compiler unroll the code versus manually that required more iterations to "even out"?

   BenchmarkUpdate 500000 2996 ns/op
   BenchmarkManual 500000 4642 ns/op
   BenchmarkUnroll 1000000 2824 ns/op
[ Parent | on HN ]

There are no comments on this comment yet.