1939023 - 0.27% Base Content JS (Windows) regression on Wed December 18 2024

Status: RESOLVED WONTFIX

(Core :: DOM: Security, defect)

Description

[Treeherder Bug Filer]

Perfherder has detected a awsy performance regression from push 2e1c3fe92eea5b1ba8526e14f4c2961c8e9e0676. 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-2009-shippable-qr	fission	1,526,303.67 -> 1,530,440.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 43147

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

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

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

Comment 2

[Benjamin Beurdouche [:beurdouche]]

No action needed. This regression is expected, has been discussed, and has been minimized already (through removing all external crypto dependencies and spending a lot of time re-plugging everything on top of NSS).

Comment 3

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

It has been over 7 days with no activity on this performance regression.

:beurdouche, since you are the author of the regressor, bug 1900537, which triggered this performance alert, could you please provide a progress update?

If this regression is something that fixes a bug, changes the baseline of the regression metrics, or otherwise will not be fixed, please consider closing it as WONTFIX. See this documentation for more information on how to handle regressions.

For additional information/help, please needinfo the performance sheriff who filed this alert (they can be found in comment #0), or reach out in #perftest, or #perfsheriffs on Element.

For more information, please visit BugBot documentation.

Comment 4

[Benjamin Beurdouche [:beurdouche]]

This can be resolved WONTFIX as mentioned in C2.

Comment 5

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

A comment containing a reason for why the performance regression was resolved as WONTFIX could not be found. It should provided when the status of the bug is changed.

:lizzard, since you resolved this bug, could you provide a comment explaining the resolution? If one has already been provided, this needinfo can be ignored/removed.

If you need additional information/help, reach out in #perftest, or #perfsheriffs on Element.

For more information, please visit BugBot documentation.