1952488 - 0.27% Base Content JS (Windows) regression on Wed March 5 2025

Status: NEW

(Web Compatibility :: Interventions, defect)

Description

[Treeherder Bug Filer]

Perfherder has detected a awsy performance regression from push 58d44279a23ddb24a9a50968ca5341a8ad12c582. 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)
0.27%	Base Content JS	windows11-64-24h2-shippable	fission	1,540,672.00 -> 1,544,768.00

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 44214

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

[Thomas Wisniewski [:twisniewski]]

There is little for us to do here, as the patch doesn't do anything new or interesting which should raise base JS any more significantly than any other such webcompat intervention, and we want this fix (we received quite a few user reports which triggered it). Because the amount seems relatively low to me, I think we can ignore this, as it would probably be worse for Formula 1 TV to not work for our Linux users.