Closed Bug 1932867 Opened 1 year ago Closed 1 year ago

1577.61 - 3.92% google-slides largestContentfulPaint / bing-search PerceptualSpeedIndex + 16 more (Windows) regression on Sat November 16 2024

Categories

(Core :: Widget: Win32, defect)

defect

Tracking

()

RESOLVED FIXED
134 Branch
Tracking Status
firefox-esr115 --- unaffected
firefox-esr128 --- unaffected
firefox132 --- unaffected
firefox133 --- unaffected
firefox134 --- fixed

People

(Reporter: intermittent-bug-filer, Unassigned)

References

(Regression)

Details

(Keywords: perf, perf-alert, regression)

Perfherder has detected a browsertime performance regression from push 1893713e1d17f24aee75b0193a03d227cb8c07b4. 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
1578% google-slides largestContentfulPaint windows11-64-shippable-qr fission warm webrender 62.89 -> 1,055.01 Before/After
1373% google-slides largestContentfulPaint windows11-64-shippable-qr fission warm webrender 66.05 -> 972.73 Before/After
414% imdb ContentfulSpeedIndex windows11-64-shippable-qr cold fission webrender 422.75 -> 2,171.79 Before/After
406% imdb LastVisualChange windows11-64-shippable-qr fission warm webrender 1,142.55 -> 5,782.49 Before/After
342% imdb PerceptualSpeedIndex windows11-64-shippable-qr fission warm webrender 201.24 -> 890.37 Before/After
341% imdb SpeedIndex windows11-64-shippable-qr fission warm webrender 196.67 -> 866.59 Before/After
269% imdb ContentfulSpeedIndex windows11-64-shippable-qr fission warm webrender 207.66 -> 766.00 Before/After
199% imdb LastVisualChange windows11-64-shippable-qr cold fission webrender 2,138.49 -> 6,401.68 Before/After
182% imdb PerceptualSpeedIndex windows11-64-shippable-qr cold fission webrender 419.18 -> 1,181.71 Before/After
107% imdb SpeedIndex windows11-64-shippable-qr cold fission webrender 431.12 -> 890.33 Before/After
... ... ... ... ... ...
7% expedia SpeedIndex windows11-64-shippable-qr cold fission webrender 500.08 -> 537.45 Before/After
7% speedometer3 TodoMVC-Svelte-Complex-DOM/DeletingAllItems/Sync windows11-64-shippable-qr fission webrender 1.05 -> 1.12 Before/After
7% google-slides ContentfulSpeedIndex windows11-64-shippable-qr fission warm webrender 698.50 -> 744.08 Before/After
5% speedometer3 TodoMVC-Preact-Complex-DOM/CompletingAllItems/Sync windows11-64-shippable-qr fission webrender 1.42 -> 1.49 Before/After
4% bing-search PerceptualSpeedIndex windows11-64-shippable-qr bytecode-cached fission warm webrender 316.12 -> 328.50 Before/After

Improvements:

Ratio Test Platform Options Absolute values (old vs new) Performance Profiles
26% wikipedia LastVisualChange windows11-64-shippable-qr fission warm webrender 575.82 -> 423.68 Before/After
25% wikipedia LastVisualChange windows11-64-shippable-qr cold fission webrender 1,033.31 -> 776.30 Before/After
13% instagram ContentfulSpeedIndex windows11-64-shippable-qr cold fission webrender 324.38 -> 281.88 Before/After
11% wikipedia loadtime windows11-64-shippable-qr fission warm webrender 250.12 -> 223.01 Before/After
6% youtube ContentfulSpeedIndex windows11-64-shippable-qr cold fission webrender 831.27 -> 783.48 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 42760

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 bacasandrei@mozilla.com.

Flags: needinfo?(emilio)

The changes have been backedout, and this bug can be closed. No further action is required from the author.

Yes, indeed, fixed by backout.

Status: NEW → RESOLVED
Closed: 1 year ago
Flags: needinfo?(emilio)
Resolution: --- → FIXED
Target Milestone: --- → 134 Branch
You need to log in before you can comment on or make changes to this bug.