Closed Bug 1886163 Opened 3 months ago Closed 3 months ago

0.84 - 0.67% Base Content JS / Base Content JS + 2 more (Linux, OSX, Windows) regression on Wed March 13 2024

Categories

(Core :: JavaScript: GC, defect)

defect

Tracking

()

RESOLVED WONTFIX
Tracking Status
firefox-esr115 --- unaffected
firefox124 --- unaffected
firefox125 --- wontfix
firefox126 --- wontfix

People

(Reporter: fbilt, Unassigned)

References

(Regression)

Details

(Keywords: perf, perf-alert, regression)

Perfherder has detected a awsy performance regression from push d46c439f53ee9a8ba6a123e75921634e31ab6473. 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)
1% Base Content JS linux1804-64-shippable-qr fission 1,501,088.00 -> 1,513,643.33
1% Base Content JS windows11-64-2009-shippable-qr fission 1,508,144.00 -> 1,519,402.00
1% Base Content JS linux1804-64-shippable-qr fission 1,501,252.00 -> 1,511,990.67
1% Base Content JS macosx1015-64-shippable-qr fission 1,505,360.00 -> 1,515,442.67

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 these tests on try with ./mach try perf --alert 41877

For more information on performance sheriffing please see our FAQ.

Flags: needinfo?(jcoppeard)

This increase is expected because we're reporting the memory for Zone objects now. There is an equivalent drop in Base Content Heap Unclassified.

Status: NEW → RESOLVED
Closed: 3 months ago
Flags: needinfo?(jcoppeard)
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.