SocketCluster – WebSockets that scale to 100K messages per second on 8 cores

From their readme-<p>&quot;The test was only set to reach up to 100 concurrent connections (each sending 1000 messages per second) - Total of 100K messages per second.&quot;<p>So they had only 100 concurrent connections.

Is 100K mps on <i>8 cores</i> considered high for node&#x2F;websockets microbenchmarking of the socket path?<p>That doesn&#x27;t seem like much from past experience writing high-throughput messaging code, and all this is doing is spitting out length-framed messages to a socket.

This is interesting, how does it compare to using nginx(or another proxy) in front of multiple socket.io instances on the same machine?

There&#x27;s also sockjs (<a href="http://sockjs.org" rel="nofollow">http:&#x2F;&#x2F;sockjs.org</a>) which has some rather impressive benchmark results when using the python&#x2F;tornado server with PyPy (<a href="http://mrjoes.github.io/2011/12/15/sockjs-bench.html" rel="nofollow">http:&#x2F;&#x2F;mrjoes.github.io&#x2F;2011&#x2F;12&#x2F;15&#x2F;sockjs-bench.html</a>). 155,000-195,000 messages per second on a single core.

It&#x27;d be nice to compare it with: <a href="https://github.com/automattic/socket.io-redis" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;automattic&#x2F;socket.io-redis</a><p>I wrote an example application using it here: <a href="https://github.com/guille/weplay" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;guille&#x2F;weplay</a>

Why does each worker need a seperate store process? It seems on an 8 core machine max worker count can only be 3 (1 master, 3 workers, 3 stores). If workers had in-memory stores -or at least connect to a Redis server-, with 4 more workers performance should increase.

Do you think Golang can handle more connections than NodeJS?