3 ms·
"I expected Go to kick Erlang's ass in the performance department but the message latency was much higher than Erlang's latency and we had 225 unhappy customers
by jerf 14y ago
"I expected Go to kick Erlang's ass in the performance department but the message latency was much higher than Erlang's latency and we had 225 unhappy customers."
Go is neat and I hope to see it succeed and thrive, but it is simply unavoidable that Erlang has existed for much longer, has been getting tuned for much longer, and this sort of thing is its monomaniacal focus whereas Go is spread a bit more thinly at the moment. Go is trying to be a systems language, Erlang very much isn't.
- lemming 14y agoWhat was surprising was how much faster the Java implementation was than Go. I expected it to be competitive but I didn't expect it to perform much better.
- deleted 14y ago[deleted]
- zemo 14y agohis 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.
- dchest 14y agoThat big difference can't be right. There's something wrong somewhere, possibly in Go's websockets implementation (which I think haven't been update for a while).
- jerf 14y agoTo you and zemo's point, those are specific instantiations of the general point I'm making. I'm sure Go will get there, as long as it stays alive, but it shouldn't be a surprise that Erlang is more polished at the moment. That's not a criticism of Go per se, it's just an effect of where they are in their lifespans. Erlang is basically mature and just polishing, and Go's still a rambunctious early teen with a wide-open future.
- dchest 14y agoI agree with this, however I'm specifically pointing out that this is not about polish of Go in general sense -- while there's a lot things to improve in the compiler, etc., in this instance, there's something wrong somewhere, perhaps in websockets library. It doesn't mean that there's something wrong with Go per se. Note that websockets is not included in the standard library yet.
- zemo 14y agohe's using io.Copy in the main websocket handler, which is a generic, buffered routine for manipulating byte buffers. I don't know if the other implementations are buffered in this manner. It's likely that there are ways to improve the Go source. Erlang is significantly more established, but I'm wary of judging technologies on their technological merits alone. Although the technical merits of Erlang are very interesting, I've been quite happy with my experiences using Go.
- ericmoritz 14y agoFeel free to fix the go version and submit a pull request. My implementation is just copy pasta from the net.