The January 2013 summary of performance measures for Firefox for Android. This month’s highlights:
- new tool to track memory use: https://www.areweslimyet.com/mobile/
- improvements in eideticker’s “Cold startup to about:home” and tp4m_nochrome
- gradual regression in tp4m_main_rss_nochrome
Talos
This section shows Perfomatic graphs from graphs.mozilla.org for mozilla-central builds of Native Fennec (Android opt). The test names shown are those used on tbpl. See https://wiki.mozilla.org/Buildbot/Talos for background on Talos.
Some of these graphs are difficult to read because the scale of the y-axis is completely inappropriate; we’re *still* working on that (see bug 705293).
tcheckerboard
Simple measure of “checkerboarding”. Lower values are better.
0.03 (start of month) – 0.00 (end of month).
Improvement -> 0.00 (Jan 30)
tcheck2
Measure of “checkerboarding” during simulation of real user interaction with page. Lower values are better.
5.0 (start of month) – 5.0 (end of month).
trobopan
Panning performance test. Value is square of frame delays (ms greater than 25 ms) encountered while panning. Lower values are better.
12000 (start of month) – 12000 (end of month).
Improvement -> 8000 (Jan 9)
Regression -> 12000 (Jan 19) Bug 833000
tprovider
Performance of history and bookmarks’ provider. Reports time (ms) to perform a group of database operations. Lower values are better.
375 (start of month) – 375 (end of month).
tsvg_nochrome
Page load test for svg. Lower values are better.
4100 (start of month) – 4100 (end of month).
tp4m_nochrome
Generic page load test. Lower values are better.
880 (start of month) – 730 (end of month).
Gradual improvement + bug 831123
tp4m_main_rss_nochrome
88000000 (start of month) – 96000000 (end of month).
Gradual regression + bug 836429
tp4m_shutdown_nochrome
28000000 (start of month) – 28000000 (end of month).
ts
Startup performance test. Lower values are better.
4200 (start of month) – 4000 (end of month).
ts_shutdown
Shutdown performance test. Lower values are better.
28000000 (start of month) – 28000000 (end of month).
Throbber Start / Throbber Stop
These graphs are taken from http://mrcote.info/phonedash/#/. 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.
Regression in time to throbber stop on Jan 3: bug 827361.
Regression in time to throbber stop on Jan 23 (intermittent, Nexus S): bug 836886.
Eideticker
These graphs are taken from http://eideticker.wrla.ch. 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
awsy
Beginning this month, we start tracking awsy (are we slim yet?) for mobile. See https://www.areweslimyet.com/mobile/ for content and background information.
