{"time": "2012-08-30 17:28:07,525", "level": "INFO ", "name": "stats", "message": {"url": "/p/slashmobdeploy/code/ci/6cac017cf4e182af52aa5af6853c16946876184b/", "uptime": 2710, "request_category": "git", "timings": {"total": 94767, "markdown": 1, "ming": 137, "jinja": 293, "mongo": 39}}}
This page takes a terribly long total time to render, but none of the individual timings are very high. We should have more instrumented functions to help identify what is taking so long.
SVN too.
{"time": "2012-10-17 08:10:30,681", "level": "INFO ", "name": "stats", "message": {"url": "/p/elec3609/code/9/", "uptime": 1473, "request_category": "svn", "timings": {"markdown": 1, "jinja": 50, "ming": 262, "socket_write": 0, "socket_read": 1149, "total": 473656, "mongo": 152}}}
Filesystem IO would be my guess as to what we need to measure.
And HG:
Adding a timing for the sidebar would be interesting. I don't think it's the main cause here, but listing all the branches & their commit counts could take some time.
Bumping to p2 since this SCM browse slowness is a broad problem
forge:tv/4832
Also review HEAD on the timermiddleware repo.
Siteops ticket for new package: https://trac.geek.net/trac/siteops/ticket/52840