97
edits
Necko/MobileCache/MicroBenchmarks: Difference between revisions
Jump to navigation
Jump to search
Necko/MobileCache/MicroBenchmarks (view source)
Revision as of 10:51, 11 September 2011
, 11 September 2011→Wanted tests
| Line 170: | Line 170: | ||
Unordered and informal list of tests we may also want to create | Unordered and informal list of tests we may also want to create | ||
; variation of the other tests where we start out with a full cache: i.e. investigate if there is a significant impact of evicting entries while we use the cache | |||
; measure time to search a cache: mem- and disk-only, but also the combination of them I believe. Make sure we search the cache without finding the entry. | ; measure time to search a cache: mem- and disk-only, but also the combination of them I believe. Make sure we search the cache without finding the entry. | ||
; identify entry-size where disk-cache is clearly slower than mem-cache: probably OS- or device-specific but it may be worth finding in case we can learn something general from it | ; identify entry-size where disk-cache is clearly slower than mem-cache: probably OS- or device-specific but it may be worth finding in case we can learn something general from it | ||
; driver which can take a list of resources and measure time to load them all: we can extract this info from e.g. Talos or by using telemetry, and it should probably be hierarchical (some resources causes other to load) | ; driver which can take a list of resources and measure time to load them all [<i>Bjarne works on this</i>]: we can extract this info from e.g. Talos or by using telemetry, and it should probably be hierarchical (some resources causes other to load) | ||