Re:How We Built Uber’s Highest Query per Second Service Usin...
by _ph_ on Wednesday March 02, 2016 @02:19AM
(#11208534)
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.
Re:How We Built Uber’s Highest Query per Second Service Usin...
by hughw on Thursday March 03, 2016 @12:33PM
(#11218382)
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.
Re:How We Built Uber’s Highest Query per Second Service Usin...
by artursapek on Wednesday March 02, 2016 @02:04PM
(#11212140)
Exactly. Build it and then benchmark the binary. Nobody uses `go run` in production.
Re:How We Built Uber’s Highest Query per Second Service Usin...
by hughw on Thursday March 03, 2016 @10:55AM
(#11217600)
$ go build vmadd.go
$ ./vmadd
1.106074715
This is a 2013 Core i7 15" MBP
Re:How We Built Uber’s Highest Query per Second Service Usin...
by hughw on Thursday March 03, 2016 @12:34PM
(#11218386)
I'd rather be right, than have karma.
My question isn't silly. I just now wrote two short programs, one in Go and one Javascript, to run a vector multiply and add on two length 1000 vectors, a million times. The JS program is faster.
Result (in seconds):
JS code: https://gist.github.com/hwinkler/62c9da0d9f2d8c7981b0Go code: https://gist.github.com/hwinkler/d234bb62b2c5fa081a50