Closed Bug 1729296 Opened 3 years ago Closed 3 years ago

27.76 - 24.96% twinopen ext+twinopen:twinopen.html / twinopen ext+twinopen:twinopen.html + 2 more (Linux) regression on Thu September 2 2021

Categories

(Core :: XPCOM, defect)

defect

Tracking

()

RESOLVED FIXED
94 Branch
Tracking Status
firefox-esr78 --- unaffected
firefox-esr91 --- unaffected
firefox92 --- unaffected
firefox93 --- wontfix
firefox94 --- fixed

People

(Reporter: aesanu, Unassigned)

References

(Regression)

Details

(4 keywords)

Perfherder has detected a talos performance regression from push 14abef8826d0c8d5d8bfdc7bfd9c081b02dc59de. 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)
28% twinopen ext+twinopen:twinopen.html linux1804-64-shippable-qr e10s stylo webrender-sw 93.65 -> 119.66
26% twinopen ext+twinopen:twinopen.html linux1804-64-shippable-qr e10s fission stylo webrender 108.37 -> 136.96
25% twinopen ext+twinopen:twinopen.html linux1804-64-shippable-qr e10s fission stylo webrender 109.17 -> 136.55
25% twinopen ext+twinopen:twinopen.html linux1804-64-shippable-qr e10s stylo webrender 105.47 -> 131.79

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 offending patch(es) will be backed out in accordance with our regression policy.

For more information on performance sheriffing please see our FAQ.

Flags: needinfo?(pbone)

I can't see the perf differences because of Bug 1729057.

Depends on: 1729057

Hi Paul, I believe the bug from comment 1 is fixed now. Can you please take another look?

Set release status flags based on info from the regressing bug 1727960

Status: NEW → RESOLVED
Closed: 3 years ago
Flags: needinfo?(pbone)
Resolution: --- → FIXED
Target Milestone: --- → 94 Branch
Has Regression Range: --- → yes
You need to log in before you can comment on or make changes to this bug.