Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Go run first compiles the code and builds an executable. You are mostly benchmarking for both systems the compilation time. Building an executable in Go takes most of a second. A significant benchmark would check the run times.


No, if you examine the code, you'll see the timer times only the accumulated execution time for the loop. The code has been compiled. See below to eliminate doubt -- I used go build and got similar numbers.


Exactly. Build it and then benchmark the binary. Nobody uses `go run` in production.


  $ go build vmadd.go
  $ ./vmadd
  1.106074715
This is a 2013 Core i7 15" MBP


I'd rather be right, than have karma.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: