Hacker News Reader

I checked the benchmark code out. I have asked the author for more information. I am not sure if all the tests were limited to using only 1 core during the run. GOMAXPROCS=1 severely limits the Go version.

1 Go worker process can utilise all the cores in the server. I just want to get that clarified.

View on HN

From the article:

> To be fair all the contestants (including Go) were running single worker process

That seems to imply that they were all limited to a single core.

A single worker process sounds like what it says it is. A single process containing possibly many OS threads. Just because it's a single process doesn't mean it won't use all cores. Where's the implication that process = core? GOMAXPROCS defaults to the number of cores in the system.

GOMAXPROCS is the number of cores used.

Reply on news.ycombinator.com