97
edits
Necko/MobileCache: Difference between revisions
Jump to navigation
Jump to search
→Collecting data to figure out why HTTP disk cache is slow on fennec
| 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 [[Mobile/Cache#Effect_of_Cache_Size]]. We need much more detailed information about what's going on. So we need to write and run some microbenchmarks that will test our current theories and quantify what (if any) performance cost they may have. For further details please visit [[Necko/MobileCache/MicroBenchmarks]]. | So far we only have aggregate data (tp4 runs) that shows the cache is often a perf loss on mobile - see [[Mobile/Cache#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. | |||
We need much more detailed information about what's going on. So we need to write and run some microbenchmarks that will test our current theories and quantify what (if any) performance cost they may have. For further details please visit [[Necko/MobileCache/MicroBenchmarks]]. | |||
At some point we're also going to want to have not just microbenchmarks, but also tests that run against a "realistic browsing history", so we can see if various code improvements actually help things, and by how much. We should start building that infrastructure now. | At some point we're also going to want to have not just microbenchmarks, but also tests that run against a "realistic browsing history", so we can see if various code improvements actually help things, and by how much. We should start building that infrastructure now. | ||