> Doing 10 runs of each and averaging the reported duration
I wish people would stop doing that. Your program is doing the same work in all benchmarking runs; any variance in the runtime is a result of factors you're probably not interested in measuring, like kernel scheduling nuances or what CPUs your benchmark happened to run on. You should take the min of microbenchmark duration, not the average.
How do you install multiple versions of Go on a single machine?
Re:Go 1.1 performance improvements
by JulienSchmidt on Tuesday May 21, 2013 @10:00AM
(#5743635)
Just install them in different paths. You have three options then:
1. Use absolute paths for the Go tools: $ /home/paul/go-tip/bin/go run myfile.go
2. Set the GOPATH every time accordingly (script)
3. Rename the folder. For example on my Windows PC I have GOPATH pointed to D:/dev/go. In the dev folder I have Go installations in go/ (currently 1.1), go1.0.3 (guess the version) and go-tip. If I want to use another version I just rename the folder to go/
Doing 10 runs of each and averaging the reported duration I see:
So, in my test Go 1.1 (represented by 9d60132d7784) is 10% faster than a previous version from March.Tests were done on a AMD64 Linux.