Talk:Incidents/2019-03-01 proton

Thanks ops for handling it!

Proton is still shadowing Electron, right? So

1. does this mean that Proton could not keep up but Electron could? That seems surprising given that they only differ in their method of remote-controlling the headless Chromium instance actually doing the rendering; plus Proton actually has a queue system for limiting the number of simultaneous renders, while AFAIK Electron doesn't.
2. did this affect availability of the PDF endpoint? Again, that would be suprising since it should only be getting mirrored traffic and is on a separate server.
3. in theory the queue system in Proton should be able to handle high load; do we understand where that went wrong? (Was the traffic so high that the queue manager itself got overloaded? 10 reqs/s does not seem like a big deal for a node service that only does scheduling.)

--tgr (talk) 18:22, 1 March 2019 (UTC)

Seems like this is not a good place to get attention so moved to T217724. --tgr (talk) 07:25, 6 March 2019 (UTC)