WebSocket benchmarks

"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."<p>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.

When benchmarking language performance results, it's a good practice to explain why is one language faster than the other. In other words, profile and figure out the bottleneck.<p>If you don't know why, then it's better not to post them until you figure out the bottlenecks. There could be factors in your environment that can affect one language and not the other which you are not aware of. Publishing such number will confuse people.

This node.js version is most certainly faster <a href="https://github.com/Weltschmerz/wsdemo/blob/master/competition/wsdemo.js" rel="nofollow">https://github.com/Weltschmerz/wsdemo/blob/master/competitio...</a><p>Wondering how much!

Not surprised to see Erlang come out on top. As I understand it, this is precisely the type of problem Erlang is good at - doing lots of little lightweight things with minimal overhead.

Python network programs, especially ones with many connections, should use Twisted.<p>A benchmark of anything but the best library/tools in each language is pointless.

I'd love to see numbers for my hellepoll on that configuration.<p><a href="https://github.com/williame/hellepoll" rel="nofollow">https://github.com/williame/hellepoll</a><p><a href="http://williamedwardscoder.tumblr.com/post/18200335569/the-history-of-hellepoll" rel="nofollow">http://williamedwardscoder.tumblr.com/post/18200335569/the-h...</a><p><a href="http://williamedwardscoder.tumblr.com/post/13590981677/performance-lessons-for-http-sockets" rel="nofollow">http://williamedwardscoder.tumblr.com/post/13590981677/perfo...</a>

This initial release is not meant to be definitive. I welcome pull requests for better implementations in your language/platform of choice and any suggestion to better tune Linux for these tests.

Pretty neat. I'm going to fork it and throw it against my C# implementation (<a href="http://www.alchemywebsockets.net" rel="nofollow">http://www.alchemywebsockets.net</a>) on mono and see how it compares.

Looking at <a href="https://github.com/ericmoritz/wsdemo" rel="nofollow">https://github.com/ericmoritz/wsdemo</a> it seems he's using his own erlang ws implementation and using a third party library for all the others?<p>If this is correct, then it's no big surprise that he does well in his own benchmark that he's developing against.

did I miss something or the methodology lacks a warm up step?<p>What I mean is, I'd expect a first run of 5 mins to warm up the servers, than another one to actually get the data.<p>Otherwise, while averages will be mostly the same, numbers like the dropped connections _could_ be misleading.

With websocket connections, provided the latency is low enough, memory usage is a bigger concern.