4 ms·
Hmm ... it should work that way now. In fact, only admin users can force a page to refresh its cached content. Though we are getting a spike in traffic with th
by groovecoder 13y ago
Hmm ... it should work that way now. In fact, only admin users can force a page to refresh its cached content.
Though we are getting a spike in traffic with the redesign launch, New Relic still reports app server response times of <600ms. But WebPagetest confirms really slow load times. [1]
If anyone finds some gross offenders of page performance, please file a bug: http://bugzilla.mozilla.org/form.mdn http://bugzilla.mozilla.org/form.mdn or better yet - send a pull request: https://github.com/mozilla/kuma https://github.com/mozilla/kuma !
[1] http://www.webpagetest.org/result/131209_Z0_1Q09/ http://www.webpagetest.org/result/131209_Z0_1Q09/
- iagooar 13y agoI'm getting response times of 4-5 seconds, which I think is a lot. This is mainly static content you got there, it's the easiest scenario for aggressive content caching. Just throw in a good Memcached server and serve the whole page from cache. Add some good expiration headers + etags and the website will fly. Unless you have problems with request queueing, which would be a completely different topic.