My monthly review of Firefox for Android performance measurements.
- significant improvement in tcheck2
- significant regression in tsvgx (SVG-ASAP) – bug 944429
- more devices added to phonedash
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) – 7800 (end of period).
Measure of “checkerboarding” during simulation of real user interaction with page. Lower values are better.
30 (start of period) – 2.5 (end of period)
The regressions of October were more than reversed.
Panning performance test. Value is square of frame delays (ms greater than 25 ms) encountered while panning. Lower values are better.
140000 (start of period) – 140000 (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.
1400 (start of period) – 7500 (end of period).
Regression of Nov 27 – bug 944429
Generic page load test. Lower values are better.
700 (start of period) – 740 (end of period)
Slight regression of Nov 27 – bug 944429
Startup performance test. Lower values are better.
4300 (start of period) – 4300 (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 start was generally stable during this period.
“Time to throbber stop” measures the time from process launch to the end of the throbber animation. Smaller values are better.
Time to throbber stop was generally stable during this period.
Note that many new devices were added this month.
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
Many of the eideticker graphs were generally stable this month.
See https://www.areweslimyet.com/mobile/ for content and background information.
awsy graphs were generally stable this month.