Commit Graph

5 Commits

Author SHA1 Message Date
Kartikaya Gupta
759f2143c4 Bug 1338347 - Add code to measure the maximum number of contiguous frame drops in a compositor animation. r=botond
This value is computed directly from the longest frame length using the vsync
interval.

MozReview-Commit-ID: 9ALXBqAVyb8
2017-03-20 11:41:05 -04:00
Kartikaya Gupta
dfce288ad0 Bug 1338347 - Refactor to group fields into a per-animation data structure. r=botond
No functional changes here, just creating a struct that we will expand in the
next patch.

MozReview-Commit-ID: HlSSvtIuYU5
2017-03-20 11:41:05 -04:00
Kartikaya Gupta
ff4ffd35eb Bug 1338347 - Record frame throughput ratio for APZ animations r=botond
MozReview-Commit-ID: 7Ljaya9RFeo
2017-03-20 11:41:05 -04:00
Kartikaya Gupta
6b5a47fd52 Bug 1338347 - Record frame throughput ratios for compositor animations r=botond
This augments the AnimationMetricsTracker to also track compositor animations
triggered by chrome and content layers separately. During the animation, the
tracker keeps a count of frames composited, and once the animation ends, it
uses the wall-clock time and vsync interval to compute the expected number of
composited frames. It then submits a ratio of actual/expected to telemetry.
A score of 1000 (because the ratio is scaled up to an integer between 0 and 1000)
indicates a perfect score with no frames dropped. Lower values are worse, and
values significantly above 1000 indicate abnormal behaviour. Values may be slightly
above 1000 due to rounding error or vsync jitter.

MozReview-Commit-ID: 30Vw0j3dm9G
2017-03-20 11:41:05 -04:00
Kartikaya Gupta
cd1c5dc857 Bug 1339220 - Add telemetry probes to measure duration and max-area of animations in the compositor. r=botond,bsmedberg
MozReview-Commit-ID: KyvsNSTcxG8
2017-02-16 14:40:37 -05:00