Hacker News Reader

Thanks 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.

I’m really excited for Ractors in this content and how/if they could improve the Ruby side

I've had good success with AnyCable

> 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?

I remember there were still latency issues, with 99th percentile being well over 100ms.

Cant find the link to the article though.