Re:I Miss Rails
by jrochkind1 on Thursday March 28, 2019 @11:05PM
(#19518808)
I'm interested in hearing about applications successfully using ActionCable for what and how. It's unclear to me how much use it's getting, or how well it meets actual use cases.
[ Parent
| on HN ]
ActionCable is super easy to use out of the box to get WebSockets running, but it's incredibly non-performant. Anything more than 100 concurrent users took the time taken to a send a message to the socket from milliseconds to seconds. Replacing it with the AnyCable gem in conjunction with AnyCable-Go got us to over 1000 concurrent users without a hitch.
Is Redis the bottleneck?
Nope it was Ruby / Rails itself.
Was it an issue with Passenger and the number of concurrent connections it could hold?
Re:I Miss Rails
by sickcodebruh on Friday March 29, 2019 @08:32AM
(#19521031)
I just deployed ActionCable into production yesterday. I’ll be using it to share some information between our users’ mobile app and our web client.
I’m concerned about performance. As much as I know that premature optimization is the Devil, it’s hard to stomach deploying something that is so notorious for becoming a bottleneck. Once I get past my MVP of this feature and have some maintenance hours budgeted, I plan on exploring AnyCable.