1962342 - 0.26 - 0.25% Base Content JS / Base Content JS (Linux, Windows) regression on Tue April 15 2025

Status: RESOLVED WONTFIX

(WebExtensions :: General, defect)

Description

[Treeherder Bug Filer]

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

Please acknowledge, and begin investigating this alert within 3 business days, or the patch(es) may be backed out in accordance with our regression policy. Our guide to handling regression bugs has information about how you can proceed with this investigation.

If you have any questions or need any help with the investigation, please reach out to [e-mail]. Alternatively, you can find help on Slack by joining #perf-help, and on Matrix you can find help by joining #perftest.

Regressions:

Ratio	Test	Platform	Options	Absolute values (old vs new)
0.26%	Base Content JS	windows11-64-24h2-shippable	fission	1,558,000.00 -> 1,562,026.67
0.25%	Base Content JS	linux1804-64-shippable-qr	fission	1,551,888.67 -> 1,555,823.33

Details of the alert can be found in the alert summary, including links to graphs and comparisons for each of the affected tests.

If you need the profiling jobs you can trigger them yourself from treeherder job view or ask [e-mail] to do that for you.

You can run all of these tests on try with ./mach try perf --alert 44778

The following documentation link provides more information about this command.

Comment 1

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

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

Comment 2

[Tomislav Jovanovic :zombie]

Based on bug 1958807 comment 4, this is small, expected, and likely to go away in the future, so I would close as wontfix.

Comment 3

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

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

Comment 4

[Tomislav Jovanovic :zombie]

Closing as wontfix per comment 2.