Re:Show HN: 2M fully loaded concurrent WebSockets
by timwis on Tuesday May 07, 2019 @04:14AM
(#19847470)
Thought this was gonna be about elixir
[ Parent
| on HN ]
Re:Show HN: 2M fully loaded concurrent WebSockets
by nelsonic on Tuesday May 07, 2019 @06:28AM
(#19848069)
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
by bsaul on Tuesday May 07, 2019 @09:09AM
(#19848989)
I'm very interested in the "seamless DevOps" part. Could you point me to some link describing how you manage to achieve that with phoenix ? (do you use docker + kubernetes, or OTP, or something else ?)
Re:Show HN: 2M fully loaded concurrent WebSockets
by arc_of_descent on Tuesday May 07, 2019 @11:30AM
(#19850427)
Have a look at distillery for building Elixir releases, and edeliver for deployment.
Re:Show HN: 2M fully loaded concurrent WebSockets
by nelsonic on Tuesday May 07, 2019 @08:02PM
(#19854635)
As others have suggested, use Distillery + Edeliver for zero-downtime deployment.
Step-by-step instructions here: https://git.io/fjcVz (happy to answer any questions you have, please open issues on GitHub as we have no way of checking notifications on HN)