Some more info to save you from reading through the bug: tp4m loads a sequence of 21 popular pages, then loads the same sequence of pages again in the same order, and reports the average of the minimum times for each page. In practice, the minimum per-page time is very usually the second access, in part because of cache hits in the Necko memory cache.
>From a cache perspective, the access pattern does not reflect real-world use >in that: - every page that is loaded is guaranteed to be loaded again - every page has the same access frequency - pages are loaded in the same order each time My simplistic approach for an improved cache-oriented page load test is to change -tpcycles from 2 to 1 (load each url in the manifest once) and change the manifest to duplicate (or more) some URLs, in a "random" order. _______________________________________________ dev-tech-network mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-network
