5 ms·
It's worth pointing out that the Phoenix Web Framework (which LiveView is built on) came into being because the creator Chris McCord tried to build something li
by rkangel 6y ago
It's worth pointing out that the Phoenix Web Framework (which LiveView is built on) came into being because the creator Chris McCord tried to build something like LiveView in Ruby and eventually ran into fundamental limitations due to how concurrency was handled. He looked around, discovered Elixir and the rest is history.
I'm very interested to learn what has changed since then that made this possible, or made it work better. Or whether those problems are just being "lived with".
- bestinterest 6y agoThere's a project called AnyCable which replaces ActionCable to give Rails the real-time performance equivalent of LiveView. See this https://evilmartians.com/chronicles/anycable-actioncable-on-steroids https://evilmartians.com/chronicles/anycable-actioncable-on-... Looks like having 20,000 idle clients connected to a server sits at only 380MB and Erlang is at 737MB.
- jakswa 6y agoThanks for posting this. I need to try it out. I'm specifically curious about how it performs when a certain amount of those 20k connections are busy and generating traffic. If I'm understanding, the anycable-go connection to ruby is over RPC? So individual websocket messages generate requests to ruby? I could see this performing better for idle connections, that's for sure.
- julianrubisch 6y agoI’m really excited for Ractors in this content and how/if they could improve the Ruby side
- bpicolo 6y ago> Looks like having 20,000 idle clients connected to a server sits at only 380MB and Erlang is at 737MB. That's with Go, versus with anycable itself. Anycable-go looks like 798?
- deedubaya 6y agoI've had good success with AnyCable
- ksec 6y agoI remember there were still latency issues, with 99th percentile being well over 100ms. Cant find the link to the article though.