1942268 - 5.3% jetstream2 base64-SP-Average (Windows) regression on Mon January 13 2025

Status: RESOLVED WONTFIX

(Core :: DOM: Forms, defect)

Description

[Treeherder Bug Filer]

Perfherder has detected a browsertime performance regression from push 855cfa4c4274f83399358bf24c316d39bdc6a75a. 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
5%	jetstream2 base64-SP-Average	windows11-64-shippable-qr	fission webrender	889.89 -> 842.76	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 43336

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 1938489

Comment 2

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

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

:edgar, since you are the author of the regressor, bug 1938489, 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 3

[Edgar Chen [:edgar] (PTO until 02/09)]

I have a patch which I think it can help, but I am struggling on verifying it, see https://perf.compare/compare-results?baseRev=39bcee7b86a49e0b5f5bd8a5c4d95337e840ce08&baseRepo=try&newRev=69ca6b429e4b788c7a10be99f4636d09887f76f0&newRepo=try&framework=13. Since the regression happens only on one subtest that doesn't look too bad, I think we could accept the regression for now, I filed bug 1943983 for further investigation.