Necko/MobileCache/MicroBenchmarks: Difference between revisions

Line 40: Line 40:
; Browsing patterns (how often do users revisit sites, how deep in sites do they browse etc): We deal with this by scaling caches and implementing smart replacement-algorithms. This factor is not taken into account by microbenchmarks - only telemetry handles this.
; Browsing patterns (how often do users revisit sites, how deep in sites do they browse etc): We deal with this by scaling caches and implementing smart replacement-algorithms. This factor is not taken into account by microbenchmarks - only telemetry handles this.


Hence, current thinking is that telemetry and microbenchmarks are complementary mechanisms suitable for different purposes. Microbenchmarks will be used as described in the section above and telemetry will be used for the following
Hence, current thinking is that telemetry and microbenchmarks are complementary mechanisms suitable for optimizing different factors of cache-performance. Microbenchmarks will be used as described in the section above and telemetry will be used for the following


==== Identify general areas of interest ====
==== Identify general areas of interest ====
97

edits