My monthly review of Firefox for Android performance measurements. May highlights:
– slight regressions in tcanvasmark and trobopan
– 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 (Android 2.2 opt). The test names shown are those used on tbpl. See
This test runs the third-party CanvasMark benchmark suite, which measures the browser’s ability to render a variety of canvas animations at a smooth framerate as the scenes grow more complex. Results are a score “based on the length of time the browser was able to maintain the test scene at greater than 30 FPS, multiplied by a weighting for the complexity of each test type”. Higher values are better.
6300 (start of period) – 5700 (end of period).
Regression of May 12 – bug 1009646.
Measure of “checkerboarding” during simulation of real user interaction with page. Lower values are better.
9 (start of period) – 9 (end of period)
Panning performance test. Value is square of frame delays (ms greater than 25 ms) encountered while panning. Lower values are better.
110000 (start of period) – 130000 (end of period)
This regression just happened today and has not triggered a Talos alert yet — I don’t have a bug number yet.
Performance of history and bookmarks’ provider. Reports time (ms) to perform a group of database operations. Lower values are better.
425 (start of period) – 425 (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.
7300 (start of period) – 7300 (end of period).
Generic page load test. Lower values are better.
750 (start of period) – 750 (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).
The improvement on May 2 was due to a change in the test setup (sut vs adb).
The small regression of May 11 is tracked in bug 1018463.
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 June.