1896841 - 12.45 - 7.42% bing-search-restaurants ContentfulSpeedIndex / bing-search-restaurants PerceptualSpeedIndex + 4 more (Android) regression on Mon May 6 2024

Status: RESOLVED WONTFIX

(Core :: Audio/Video, defect)

Description

[Acasandrei Beatrice (needinfo me)]

Perfherder has detected a browsertime performance regression from push 10ac43f0b16682be690ddd0e496e94d14b0f5cd1. As author of one of the patches included in that push, we need your help to address this regression.

Regressions:

Ratio	Test	Platform	Options	Absolute values (old vs new)	Performance Profiles
12%	bing-search-restaurants ContentfulSpeedIndex	android-hw-a51-11-0-aarch64-shippable-qr	cold webrender	810.77 -> 911.75	Before/After
12%	bing-search-restaurants PerceptualSpeedIndex	android-hw-a51-11-0-aarch64-shippable-qr	cold webrender	888.97 -> 991.26	Before/After
11%	bing-search-restaurants SpeedIndex	android-hw-a51-11-0-aarch64-shippable-qr	cold webrender	872.75 -> 969.49	Before/After
10%	bing-search-restaurants LastVisualChange	android-hw-a51-11-0-aarch64-shippable-qr	cold webrender	1,664.63 -> 1,829.41	Before/After
10%	youtube loadtime	android-hw-a51-11-0-aarch64-shippable-qr	cold webrender	772.87 -> 847.44	Before/After
7%	bing-search-restaurants PerceptualSpeedIndex	android-hw-a51-11-0-aarch64-shippable-qr	cold webrender	901.03 -> 967.85	Before/After

Details of the alert can be found in the alert summary, including links to graphs and comparisons for each of the affected tests. Please follow our guide to handling regression bugs and let us know your plans within 3 business days, or the patch(es) may be backed out in accordance with our regression policy.

If you need the profiling jobs you can trigger them yourself from treeherder job view or ask a sheriff to do that for you.

You can run these tests on try with ./mach try perf --alert 230

For more information on performance sheriffing please see our FAQ.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

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

Comment 2

[Jim Mathies [:jimm]]

We moved the codec query out of startup and instead do it on demand. So this is expected.

Comment 3

[az [:az]]

The delays here match how long it takes for codec support checks to run, which is a cost that's going to be needed to be invoked at some point. I'll go ahead and close this as WONTFIX, unless jmuizelaar has any remaining concerns.