3 ms·
his reporting is very misleading. If you look at the number of messages and connections, Java only held ~5k connections, while Go held just shy of ~10k. In th
by zemo 14y ago
his reporting is very misleading. If you look at the number of messages and connections, Java only held ~5k connections, while Go held just shy of ~10k. In the same amount of time, Java was only able to facilitate the transmission of half the number of messages, so... it depends what you mean by "fast".
- stock_toaster 14y agoInterestingly, Go's "connection time" was by far the lowest. He also tested with m1.medium instances, which are single cpu. No mention if the instances were 64bit or 32bit (this may matter for Go, as the GC has some issues under 32bit currently). Tests are hard. Still nice to see a real-world-like comparison between some popular stacks. Edit: discussion on go-nuts: https://groups.google.com/group/golang-nuts/browse_thread/thread/6dc8468d6237f676 https://groups.google.com/group/golang-nuts/browse_thread/th...
- ericmoritz 14y agoI used the m1.medium instance on 64bit Ubuntu 12.04. I will update the results.md to note that. I will also rerun all the tests on 2 core 64bit instances tonight.