> However, in the particular case of enabling disk-cache > on Android (which I'm working towards) I want to see > how the disk on a device performs under stress and I > don't really need telemetry-data for that - I just want > to access the disk. Synthetic benchmarks are IMO fine > for this, and I don't have to spend time on implementing > and waiting for telemetry.
Of course micro-benchmarks can come in handy when we have a specific question about disk performance, etc. > In fact, Geoff got some interesting results a few weeks > ago suggesting that the disk actually performs ok under > normal operations - it is creating the cache which really > blows the numbers up (which seems to happen when clearing > the cache). This is IMO worth to verify or falsify, and > then perhaps use telemetry to get data of how often a user > clears/creates the cache in order to evaluate the impact > of this in real life. >From my perspective telemetry is the best way to find these perf regressions in the first place. I.e. once we've blocked the cache performance into measurable pieces, we'll be able to see which parts are slow, and which we need to work on most urgently (and possibly which things require rearchitecting). Jason _______________________________________________ dev-tech-network mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-network
