504 errors

[jmroot]

The site has been timing out or giving 504 errors for most of today. @arjunsalyan

[Dave-Allured]

I am noticing improvement in response from the webapp site, in the day or so since #391 was resolved. This removed an unintended firewall block against ports.macports.org.

@jmroot et al, can this ticket be closed? Are you now seeing a similar improvement in response?

[ryandesign]

I am also seeing normal response times now, however I wouldn't close the ticket so soon, since there seems to be a problem in the site programming where it apparently does not implement these requests to Trac asynchronously.

[arjunsalyan]

@ryandesign While the calls are asynchronous, but they hit the same server only. The uwsgi service on this server runs 6 sync workers, each call to trac could potentially block a gunicorn worker for 60 seconds (current timeout) from accepting any more requests. When all workers get busy, it would lead to 502s and 504s.

We can reduce overall timeout for uwsgi to 30 seconds, and a specific timeout for the request made to trac.macports.org somewhere between 2-5 seconds.

OR, we can also make the call to trac from the client side itself. But we might loose caching benefits.