My monthly review of Firefox for Android performance measurements.
– Regressions in tcanvasmark, tcheck2, and tsvgx; improvement in ts-paint.
– Improvements in some eideticker startup measurements.
This section tracks Perfomatic graphs from graphs.mozilla.org for mozilla-central builds of Native Fennec (Android 2.2 opt). The test names shown are those used on tbpl. See https://wiki.mozilla.org/Buildbot/Talos for background on Talos.
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.
7800 (start of period) – 7200 (end of period).
Regression on Feb 19 – bug 978958.
Measure of “checkerboarding” during simulation of real user interaction with page. Lower values are better.
2.7 (start of period) – 24 (end of period)
Regression of Feb 25: bug 976563.
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) – 110000 (end of period)
Performance of history and bookmarks’ provider. Reports time (ms) to perform a group of database operations. Lower values are better.
375 (start of period) – 375 (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.
7500 (start of period) – 7600 (end of period).
This test both improved and regressed slightly over the month, for a slight overall regression. Bug 978878.
Generic page load test. Lower values are better.
700 (start of period) – 710 (end of period).
No specific regression identified.
Startup performance test. Lower values are better.
4300 (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” measures the time from process launch to the start of the throbber animation. Smaller values are better.
“Time to throbber stop” measures the time from process launch to the end of the throbber animation. Smaller values are better.
:bc has been working on reducing noise in these results — notice the improvement. And there is more to come!
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
There is some improvement from last month’s startup measurements:
See https://www.areweslimyet.com/mobile/ for content and background information.
I did not notice any big changes this month.