To boldly go where Node man has gone before

Re:To boldly go where Node man has gone before by jgrahamc on Wednesday May 16, 2012 @02:38PM (#3983373)

It's true that Go can use multiple cores, but I was doing these tests in a Ubuntu VM that was restricted to using a single core so that Go's inherent 'multicore' advantage was dialed down. I'll add a note to the post.

[ Parent | on HN ]

Re:To boldly go where Node man has gone before by kbd on Wednesday May 16, 2012 @02:43PM (#3983394)

That's a(nother) pretty big real-world advantage for Go then, no? I know the solution for Node is to just run one instance per-core, but it's automatic with Go.

I'd love to see a second set of benchmarks of the same code on multiple cores.

[ Parent | on HN ]

Re:To boldly go where Node man has gone before by _ak on Wednesday May 16, 2012 @05:27PM (#3984104)

Yes, Go will do that automatically. Plus, you can write your code in a completely linear fashion, instead of the typical Node.js code with lots of callbacks.

[ Parent | on HN ]