1942774 - 5.9 - 3.9% damp complicated.jsdebugger.open.DAMP / damp custom.jsdebugger.open.DAMP (Linux) regression on Fri January 17 2025

Status: RESOLVED WONTFIX

(DevTools :: Debugger, defect)

Description

[Treeherder Bug Filer]

Perfherder has detected a devtools performance regression from push 3372d449dbfde6a686ed07c7d23ba8c5740b1431. 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)
6%	damp complicated.jsdebugger.open.DAMP	linux1804-64-shippable-qr	e10s fission stylo webrender	630.00 -> 667.14
4%	damp custom.jsdebugger.open.DAMP	linux1804-64-shippable-qr	e10s fission stylo webrender	722.56 -> 750.78

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 43393

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 1862157

Comment 2

[Alexandre Poirot [:ochameau]]

Bug 1862157 introduced a new feature to see service workers in the debugger.
This forces us to load some new modules and slow down initial loading of the debugger frontend.
I haven't find anything to optimize in this new code, but opened a few performance low hanging fruits in order to speed up the overall performance of the debugger.

Comment 3

[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.

:ochameau, 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.