1922788 - 11.02 - 2.08% speedometer3 cpuTimePageload / speedometer3 TodoMVC-Svelte-Complex-DOM/total + 9 more (Windows) regression on Tue October 1 2024

Status: RESOLVED FIXED

(Core :: Graphics: WebRender, defect)

Description

[Treeherder Bug Filer]

Perfherder has detected a browsertime performance regression from push 24e81e2c5ad1d3453abbbcec8d1a7507c1822669. 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
11%	speedometer3 cpuTimePageload	windows11-64-shippable-qr	fission webrender	339.12 -> 376.50	Before/After
8%	speedometer3 TodoMVC-JavaScript-ES5/CompletingAllItems/Async	windows11-64-shippable-qr	fission webrender	1.87 -> 2.02	Before/After
5%	speedometer3 TodoMVC-Svelte-Complex-DOM/DeletingAllItems/Async	windows11-64-shippable-qr	fission webrender	3.49 -> 3.66	Before/After
5%	speedometer3 TodoMVC-Preact-Complex-DOM/DeletingAllItems/Async	windows11-64-shippable-qr	fission webrender	3.21 -> 3.35	Before/After
3%	speedometer3 TodoMVC-Lit-Complex-DOM/CompletingAllItems/Async	windows11-64-shippable-qr	fission webrender	5.60 -> 5.78	Before/After
3%	speedometer3 TodoMVC-Preact-Complex-DOM/DeletingAllItems/total	windows11-64-shippable-qr	fission webrender	4.30 -> 4.44	Before/After
3%	speedometer3 TodoMVC-Vue/CompletingAllItems/Async	windows11-64-shippable-qr	fission webrender	5.95 -> 6.12	Before/After
3%	speedometer3 TodoMVC-Svelte-Complex-DOM/DeletingAllItems/total	windows11-64-shippable-qr	fission webrender	4.62 -> 4.75	Before/After
3%	speedometer3 TodoMVC-Lit-Complex-DOM/CompletingAllItems/total	windows11-64-shippable-qr	fission webrender	7.60 -> 7.81	Before/After
3%	speedometer3 TodoMVC-Vue/CompletingAllItems/total	windows11-64-shippable-qr	fission webrender	7.55 -> 7.76	Before/After
2%	speedometer3 TodoMVC-Svelte-Complex-DOM/total	windows11-64-shippable-qr	fission webrender	18.85 -> 19.24	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 all of these tests on try with ./mach try perf --alert 2304

The following documentation link provides more information about this command.

For more information on performance sheriffing please see our FAQ.

If you have any questions, please do not hesitate to reach out to [e-mail].

Comment 1

[Donal Meehan [:dmeehan]]

Setting 133 to fixed since the regressor was backed out of central
https://bugzilla.mozilla.org/show_bug.cgi?id=1917493#c9

Comment 2

[Erich Gubler [:ErichDonGubler]]

I'm not certain of the severity we want to assign. Tentatively assigning S3, with escalation to triage.

Comment 3

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

:gw, since you are the author of the regressor, bug 1917493, could you take a look?

For more information, please visit BugBot documentation.

Comment 4

[Glenn Watson [:gw]]

This was backed out - will investigate before relanding.