Confirmed users
96
edits
Todesschaf (talk | contribs) |
Todesschaf (talk | contribs) |
||
| Line 16: | Line 16: | ||
== Collecting data to figure out why HTTP disk cache is slow on fennec == | == Collecting data to figure out why HTTP disk cache is slow on fennec == | ||
So far we only have aggregate data (tp4 runs) that shows the cache is often a perf loss on mobile - see [[ | So far we only have aggregate data (tp4 runs) that shows the cache is often a perf loss on mobile - see [[Necko/MobileCache#Effect_of_Cache_Size]]. | ||
* bjarne: note that this test is limited in that it cyclically loads a limited pageset, and it keeps the memory-cache at 1Mb. Effectively it says "When loading a relatively small pageset over-and-over again on mobile, a 1Mb memory-cache is often more efficient than a disk-cache." Given that the cache-service prefers using a disk-cache over a memory-cache, and the memory-cache uses a more sophisticated replacement-algorithm than the disk-cache (see {{bug|648605}} and {{bug|693255}}) this is not surprising. To be more conclusive we need results from running this test with the memory-cache turned off. | * bjarne: note that this test is limited in that it cyclically loads a limited pageset, and it keeps the memory-cache at 1Mb. Effectively it says "When loading a relatively small pageset over-and-over again on mobile, a 1Mb memory-cache is often more efficient than a disk-cache." Given that the cache-service prefers using a disk-cache over a memory-cache, and the memory-cache uses a more sophisticated replacement-algorithm than the disk-cache (see {{bug|648605}} and {{bug|693255}}) this is not surprising. To be more conclusive we need results from running this test with the memory-cache turned off. | ||