1797018 - Speedometer regression on Android Samsung Galaxy A51 (but not Google Pixel 2) on 2022-10-09

Status: RESOLVED WORKSFORME

(Core :: Performance: General, defect)

Description

[Chris Peterson [:cpeterson]]

Attachment: Perfherder_screenshot.png

Speedometer on Samsung Galaxy A51 (blue in the screenshot, but not Google Pixel 2, yellow in the screenshot) was bimodal (between 17-21, higher is faster) until around 2022-09-01 when it stabilized around 21. Speedometer regressed, becoming bimodal again (17-21), around 2022-10-10:

https://treeherder.mozilla.org/perfherder/graphs?highlightAlerts=1&highlightChangelogData=1&highlightCommonAlerts=0&series=autoland,4360970,1,13&series=autoland,3382860,1,13&timerange=7776000

Comment 1

[Chris Peterson [:cpeterson]]

Looks like this intermittent regression happened earlier than 2022-10-10. I'm retriggering Speedometer on some older autoland jobs to narrow the regression range.

Comment 2

[Chris Peterson [:cpeterson]]

Botond, I think your scrolling change in bug 1755044 caused this bimodal regression in Speedometer. The regression happens on the Galaxy A51 (Android 11), but not the faster Pixel 2 devices (Android 8).

Speedometer on the Galaxy A51 had been bimodal until early September (which I think was fixed by bug 1786449 reverting overscroll animations on Android <= 9).

I don't know if a Speedometer regression from 22 to 17 is severe or just noise. What do you recommend?

Comment 3

[BugBot [:suhaib / :marco]]

Set release status flags based on info from the regressing bug 1755044

Comment 4

[Chris Peterson [:cpeterson]]

Resolving as WFM because the A51's bimodality disappeared around 2022-10-27.

TODO: fix tracking flags