Closed Bug 1884885 Opened 8 months ago Closed 8 months ago

22.96 - 21.57% facebook-nav.landing LastVisualChange / facebook-nav.landing LastVisualChange (Windows) regression on Tue March 5 2024

Categories

(Core :: Audio/Video: Playback, defect)

defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: bacasandrei, Unassigned)

References

(Regression)

Details

(Keywords: perf, perf-alert, regression)

Perfherder has detected a browsertime performance regression from push d07acf022aad07a82d0c8ce9e10cb8d828d261f3. There's no need to address this regression because the changeset was backed out. This bug was filed with the purpose of acknowledging the changes.

Regressions:

Ratio Test Platform Options Absolute values (old vs new) Performance Profiles
23% facebook-nav.landing LastVisualChange windows10-64-shippable-qr cold fission webrender 1,534.01 -> 1,886.24 Before/After
22% facebook-nav.landing LastVisualChange windows10-64-shippable-qr cold fission webrender 1,524.52 -> 1,853.34 Before/After

Improvements:

Ratio Test Platform Options Absolute values (old vs new) Performance Profiles
15% youtube FirstVisualChange windows10-64-shippable-qr fission warm webrender 141.30 -> 120.65 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.

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 41757

For more information on performance sheriffing please see our FAQ.

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