13.22 - 2.57% stylebench / motionmark-htmlsuite + 1 more (Linux, Windows) regression on Tue February 14 2023
Categories
(Core :: Graphics: WebRender, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox110 | --- | unaffected |
firefox111 | --- | unaffected |
firefox112 | --- | fixed |
People
(Reporter: aesanu, Unassigned)
References
(Regression)
Details
(Keywords: perf, perf-alert, regression)
Perfherder has detected a browsertime performance regression from push 005f973722f7e65152f284acdc8989e4b820cf22. 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 |
---|---|---|---|---|---|
13% | stylebench | windows10-64-shippable-qr | fission webrender | 53.07 -> 46.05 | Before/After |
12% | stylebench | windows10-64-shippable-qr | fission webrender | 53.07 -> 46.49 | Before/After |
3% | motionmark-htmlsuite | linux1804-64-shippable-qr | fission webrender | 59.70 -> 58.17 | 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 offending 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.
Comment 1•2 years ago
|
||
Set release status flags based on info from the regressing bug 1811978
Comment 2•2 years ago
|
||
I'm going to back out the regressing patch temporarily, and fix the underlying cause of the regression that this patch exposes.
Updated•2 years ago
|
Comment 3•2 years ago
|
||
This should be resolved by the patch that was backed out above - can you confirm?
Reporter | ||
Comment 4•2 years ago
|
||
(In reply to Glenn Watson [:gw] from comment #3)
This should be resolved by the patch that was backed out above - can you confirm?
Yes, it's fixed. Thank you.
Comment 5•2 years ago
|
||
fixed by backout
Description
•