Investigate raising default webservice memory limits
Inspired by this customer ticket(internal link) (and also possibly this customer ticket (internal link) I wanted to discuss raising the default webservice memory limit GET uses.
Currently it is set to 5.25G. Since GET by default uses 4 CPUs our documentation recommends 7G as a minimum for the limit.
When under higher load this ends up causing hard to diagnose 502 errors as individual Puma workers get killed but the pod itself does not get killed or restart.
I was about to submit an MR but I wanted to raise an issue first.
Edited by Jessie Lee