My monthly review of Firefox for Android performance measurements for January 2015.
– No significant Talos regressions or improvements.
– Improvements in autophone’s “Time to throbber stop”.
This section tracks Perfomatic graphs from https://wiki.mozilla.org/Buildbot/Talos for background on Talos.for mozilla-central builds of Firefox for Android, for Talos tests run on Android 4.0 O. The test names shown are those used on treeherder. See
Measure of “checkerboarding” during simulation of real user interaction with page. Lower values are better.
18.2 (start of period) – 18.7 (end of period)
Minor regression January 12 – bug 1122012.
Panning performance test. Value is square of frame delays (ms greater than 25 ms) encountered while panning. Lower values are better.
62000 (start of period) – 70000 (end of period)
Significant noise noted; no specific regression.
Performance of history and bookmarks’ provider. Reports time (ms) to perform a group of database operations. Lower values are better.
520 (start of period) – 520 (end of period).
An svg-only number that measures SVG rendering performance. About half of the tests are animations or iterations of rendering. This ASAP test (tsvgx) iterates in unlimited frame-rate mode thus reflecting the maximum rendering throughput of each test. The reported value is the page load time, or, for animations/iterations – overall duration the sequence/animation took to complete. Lower values are better.
5900 (start of period) – 5900 (end of period).
Generic page load test. Lower values are better.
855 (start of period) – 870 (end of period).
Regression of January 15 may be reversed January 28 – no bug?
Throbber Start / Throbber Stop
These graphs are taken from http://phonedash.mozilla.org. Browser startup performance is measured on real phones (a variety of popular devices).
Time to throbber start seems steady this month.
Time to throbber stop has multiple small improvements.
These graphs are taken from http://eideticker.mozilla.org. Eideticker is a performance harness that measures user perceived performance of web browsers by video capturing them in action and subsequently running image analysis on the raw result.
More info at: https://wiki.mozilla.org/Project_Eideticker
Those all look pretty steady to me, but there’s lots more to explore — be sure to check out eideticker for yourself!