Ignoring yesterday's cock-up, half loading pages (esp in the list of boards) should be rare on OOF, due to the way the page is built.
All the contention is usually on the database server, not the web server, and by the time the boards are started to be pushed to the client, the database has returned all the boards to the web server.
The only way the web server can delay part way through the delivery of the boards is:
1) Web server under heavy load
2) It can't push the packets out due to network delays
3) Client end
WRT number 1, ignoring yesterday, web server load is near zero:
17:59:35 up 22:14, 1 user, load average: 0.06, 0.06, 0.05
this is a fairly typical figure for the webserver (the database server gets its nads caned at busy periods - but we've proved its not that)
2 is out of our hands, although IIRC chrisgixer is a VM customer, and their transparent proxies are worse than dire. There are certainly no networking delays this end.
3) Partially corrupt caches are commonplace across all browsers, and cause similar issues. Hence the first port of call is always to clear the cache. If the client is an old, slow machine, the compute power can be taken away for other things rather than rendering the page.
I certainly cannot replicate it here, even yesterday when it was plain slow, using a Windows laptop.
Author
Topic: Oof page delay (Read 3721 times)