Comment 5 for bug 302798

There's more going on than slow queries. About two-thirds of these timeouts spend less time on SQL than they do on other things—more often than not a lot less!

So this page may be acting as a canary—keeling over first when there's really a systemic problem.

There's not a huge amount of "business logic" to process for this page, so there's a good chance that the real problem is hidden somewhere on a low level: memory on the app servers, waiting for connections, missing C speedup routines to replace Python ones, plain old load..?