Investigate ActionCable memory spikes in prod
Problem
While rolling out ActionCable for real time issue assignees, we observed that Puma worker memory started spiking as the number of connections went up, eventually exceeding the thresholds we define as healthy.
This is currently blocking this feature from going live, and the feature has been disabled meanwhile.
We need to investigate what is causing this and how to remedy it.
I'm seeing high memory utilization on the pods servicing these requests
https://dashboards.gitlab.net/d/git-pod/git-pod-info?orgId=1&from=now-6h&to=now
It looks like the memory consumption is hitting our limit in under < 1 hour
Support data
Memory and AC connections during the attempted rollout:
Edited by Matthias Käppler

