Something you have to consider, this will probably make it into go 1.9: https://go-review.googlesource.com/?polygerrit=0#/c/40693/
Am Mittwoch, 19. April 2017 11:15:03 UTC+2 schrieb slinso: > > Hi all, > > I'm interested in the compiler performance of different cpus. How much > impact has the number of cores? Or is higher frequency with a few cores > better regarding compile time / $. > Maybe someone already owns a new ryzen cpu. Is it worth buying a highend > Intel cpu (i7 or xeon) for 1000$ or is the highend AMD for 500$ maybe even > better for go. > My C++ projects would benefit the most from more cores. But that's > something different because we are talking about 10 minutes or more compile > time. > > I think using Dave Cheneys compiler benchmarks (benchkube > <https://github.com/davecheney/benchkube>) and (benchjuju > <https://github.com/davecheney/benchjuju>) should provide solid base > numbers for the performance. Of course smaller projects could behave > differently. But if a small project compiles in 1s or 2s doesn't matter > that much to the development cycle. > I have not moved the codebase to a ramdisk, because i would like to see > numbers from normal dev setups. > > > go version go1.8.1 linux/amd64 > > cat /proc/cpuinfo | head | grep "model name" > model name : Intel(R) Core(TM) i7-6700T CPU @ 2.80GHz > RAM: 16GB > Disk: Samsung 850 Evo > > avg. runtime: > benchjuju: 23.7s > benchkube: 21.3s > > > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
