Show HN: 2M fully loaded concurrent WebSockets

Reminds me of the good old days when an IBM 360 running CICS could support 13,000+ terminals with just 16 MB of RAM.<p>I thought shoehorning was a microcomputer thing until I found out about that!

You may also want to check out:<p>- benchmark project repo - <a href="https:&#x2F;&#x2F;github.com&#x2F;oatpp&#x2F;benchmark-websocket" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;oatpp&#x2F;benchmark-websocket</a><p>- oatpp framework repo (the benchmark built with) - <a href="https:&#x2F;&#x2F;github.com&#x2F;oatpp&#x2F;oatpp" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;oatpp&#x2F;oatpp</a>

Your bottleneck might be packets&#x2F;sec of 150k. Soft interrupt handling is likely getting saturated. If you tune your network (receive side scaling etc) for high packet throughput, you may be able to get the benchmark to find the application bottleneck.

Thought this was gonna be about elixir

The memory seems high actually, I&#x27;ve seen other C &#x2F; C++ &#x2F; Go implementation using less than a 1GB for 1m connections. Pretty cool nonetheless!<p><a href="https:&#x2F;&#x2F;github.com&#x2F;uNetworking&#x2F;uWebSockets" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;uNetworking&#x2F;uWebSockets</a><p><a href="https:&#x2F;&#x2F;speakerdeck.com&#x2F;eranyanay&#x2F;going-infinite-handling-1m-websockets-connections-in-go?slide=35" rel="nofollow">https:&#x2F;&#x2F;speakerdeck.com&#x2F;eranyanay&#x2F;going-infinite-handling-1m...</a>

@lganzzzo great work! (bookmarked for further reading...) out of curiosity, did you consider using Rust for this before using C++? or did you dive strait into C++?

Get your credit card or your infra ready, whichever applies... someone seating here with me is about to max out botnet rush to you

Does anybody have real world experience (and maybe data) for websockets when used in a mobile environment (with a lot of dropped connections)?

I&#x27;m confused. If there are 20M clients and the server is sending 9M messages per minute, doesn&#x27;t that mean that each client is sending less than 1 message per minute?