Your bottleneck might be packets/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.
Show HN: 2M fully loaded concurrent WebSockets
11–20 of 32 posts
Re: Show HN: 2M fully loaded concurrent WebSockets
#12"This site can’t be reached oatpp.io took too long to respond."
effing LOL.
Re: Show HN: 2M fully loaded concurrent WebSockets
#13Reminds me of the good old days when an IBM 360 running CICS could support 13,000+ terminals with just 16 MB of RAM. I thought shoehorning was a microcomputer thing until I found out about that!
Is there a URL that talks more about how CICS pulled that off?
Re: Show HN: 2M fully loaded concurrent WebSockets
#14Does anybody have real world experience (and maybe data) for websockets when used in a mobile environment (with a lot of dropped connections)?
Re: Show HN: 2M fully loaded concurrent WebSockets
#15Your bottleneck might be packets/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.
How would you do that?
Re: Show HN: 2M fully loaded concurrent WebSockets
#16Thought this was gonna be about elixir
Re: Show HN: 2M fully loaded concurrent WebSockets
#17Your bottleneck might be packets/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.
How would you do that?
For UDP, this is an excellent resource: https://events.static.linuxfound.org/sites/events/files/slid...
Re: Show HN: 2M fully loaded concurrent WebSockets
#18Thought this was gonna be about elixir
Indeed the Phoenix benchmark with 2M concurrent connections https://phoenixframework.org/blog/the-road-to-2-million-webs... was on a 40core/128gb machine but the load was a pretty realistic "real world" use case.
If @lganzzzo's oatpp can indeed handle 2M concurrent on 8core/52GB with _presence_ and real data being communicated/broadcast it would be worth looking into.
We use Phoenix for a number of projects and in addition to handling lots of Websocket connections it's a fully featured framework with an excellent workflow, expressive ORM and seamless DevOps.
Seems like oatpp has been built with a single purpose in mind (similar to Redis). Always good to see people diving deep into a topic to push the boundaries of the state of the art.
Re: Show HN: 2M fully loaded concurrent WebSockets
#19@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++?
Re: Show HN: 2M fully loaded concurrent WebSockets
#20Now do it with Python and see how it goes lol