915189 - Profile Browser/Phone Janks while running the test suites.

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: General, defect)

Description

[Nicolas B. Pierron [:nbp]]

Currently we do not have any benchmark to tell us if the browser is janky or not.  One idea would be to measure the time that we take to empty the event loop.

The Gecko profiler already provide such information with some overhead, but it would be better to have metrics on datazilla on how the platform behave and on how Gaia applications behave too.

Being inspired by [1], one way to solve this problem would be to add a timestamp to each event and set a new timestamp if the queue is empty and no event are in the queue.  Otherwise copy the end-timestamp of the last user-visible change (paint, ring tone, …).

Doing so will give us a metric that we can collect during any process execution and measure the responsiveness of a browser / phone.

It would be nice to have these timestamp attach to every event and even in optimized builds as we do not much care of the responsiveness of debug version of the platform.  If the overhead of doing this all the time is too much, then we can just add a pref to prevent maintaining the timestamps fields of every event.

[1] http://www.ucc.asn.au/~mccabedj/BrowserResponsivenessBenchmark.html

Comment 1

[BMO Automation]

Firefox OS is not being worked on