Closed tsenart closed 4 years ago
Looking at the code, it seems that the only possible slowness source is Postgres. Either the initial list
query or the fact that we're doing N+1 queries after that (or both).
Dear all,
This is your release captain speaking. 🚂🚂🚂
Branch cut for the 3.13 release is scheduled for tomorrow.
Is this issue / PR going to make it in time? Please change the milestone accordingly. When in doubt, reach out!
Thank you
Another issue is that this endpoint currently returns around 1.3MB of data, most of that is base64 encoded icons.
This woke me up 3h before my alarm clock today :(
Site24x7 is frequently alerting us due to sporadic timeouts on this endpoint. To prevent on-call burnout, we should either fix this endpoint or remove this alert.
An independent Vegeta probe that ran for around a day in our tooling cluster confirms that the issue is not with Site24x7.