Closed Bug 1865819 Opened 2 years ago Closed 2 years ago

35.31% motionmark-animometer-ramp (Windows) regression on Tue November 21 2023

Categories

(Core :: Security: Process Sandboxing, defect)

defect

Tracking

()

RESOLVED FIXED
122 Branch
Tracking Status
firefox-esr115 --- unaffected
firefox120 --- unaffected
firefox121 --- unaffected
firefox122 + fixed

People

(Reporter: bacasandrei, Unassigned)

References

(Regression)

Details

(Keywords: perf, perf-alert, regression)

Perfherder has detected a browsertime performance regression from push 4a6ed43174388497963a5e476b2b22e495ba088e. 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
35% motionmark-animometer-ramp windows10-64-shippable-qr fission webrender 650.01 -> 420.50 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.

For more information on performance sheriffing please see our FAQ.

Flags: needinfo?(cmartin)

Tracking based on the size of the perf change, but can revisit once triaged

Setting Fx122 to fixed, the regressor was backed out of central

Flags: needinfo?(cmartin)

The test has returned to the same values after the backout.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 122 Branch
You need to log in before you can comment on or make changes to this bug.