My monthly review of Firefox for Android performance measurements. June highlights:
– Talos values tracked here switch to Android 4.0, rather than Android 2.2
– Talos regressions in tcheck2 and tsvgx
– small regression in time to throbber stop
– Eideticker still not reporting results.
This section tracks Perfomatic graphs from https://wiki.mozilla.org/Buildbot/Talos for background on Talos.for mozilla-central builds of Native Fennec. In all of my previous posts, this section has tracked Talos for Android 2.2 Opt. This month, and going forward, I switch to Android 4.0 Opt, since the Android 2.2 Opt tests are being phased out. The test names shown are those used on tbpl. See
This test is not currently run on Android 4.0.
Measure of “checkerboarding” during simulation of real user interaction with page. Lower values are better.
6 (start of period) – 12 (end of period)
Regression of June 17 – bug 1026742.
Panning performance test. Value is square of frame delays (ms greater than 25 ms) encountered while panning. Lower values are better.
50000 (start of period) – 50000 (end of period)
There was a large temporary regression between June 12 and June 14 – bug 1026798.
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.
6100 (start of period) – 6300 (end of period).
Regression of June 16 – bug 1026551.
Generic page load test. Lower values are better.
940 (start of period) – 940 (end of period).
Startup performance test. Lower values are better.
3600 (start of period) – 3600 (end of period).
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” looks very flat for all devices, but “Time to throbber stop” has a slight upward trend, especially for nexus-s-2 — bug 1032249.
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
Eideticker results are still not available. We’ll check back at the end of July.