Confirmed users
508
edits
Mozilla.com/2011-Rebranding-Project/Benchmarks: Difference between revisions
Mozilla.com/2011-Rebranding-Project/Benchmarks (view source)
Revision as of 18:13, 22 July 2011
, 22 July 2011→mozilla.org PHP page
| Line 82: | Line 82: | ||
[[File:mozorg-php-page.png]] | [[File:mozorg-php-page.png]] | ||
'''Conclusion''': We've actually '''increased''' the performance of mozilla.org pages by ''' | '''Conclusion''': We've actually '''increased''' the performance of mozilla.org pages by '''50ms'''! The RewriteMap+PHP solution is an obvious winner. The performance comes from converting the 1500 redirects into a more optimized RewriteMap database file. | ||
Notice the spike in the 90% range, however. Honestly I'm not sure how to explain it, but I think it's an anomaly with my testing environment. There's absolutely no reason why that should happen (5% of the requests take a lot longer to respond). If I actually ''add'' all the htacess rewrites from mozilla.org ''in addition'' to the RewriteMap database file, it doesn't spike like that. We can look into the spike later and see if it exists on our staging/live servers. These tests also perform requests at a much higher rate than mozilla.org ever sees. | Notice the spike in the 90% range, however. Honestly I'm not sure how to explain it, but I think it's an anomaly with my testing environment. There's absolutely no reason why that should happen (5% of the requests take a lot longer to respond). If I actually ''add'' all the htacess rewrites from mozilla.org ''in addition'' to the RewriteMap database file, it doesn't spike like that. We can look into the spike later and see if it exists on our staging/live servers. These tests also perform requests at a much higher rate than mozilla.org ever sees. | ||