3.31 - 3.29% google-docs loadtime / google-docs SpeedIndex (OSX) regression on Wed August 3 2022
Categories
(Core :: Graphics: Canvas2D, defect, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr91 | --- | unaffected |
| firefox-esr102 | --- | unaffected |
| firefox103 | --- | unaffected |
| firefox104 | --- | unaffected |
| firefox105 | --- | affected |
People
(Reporter: alexandrui, Unassigned)
References
(Regression)
Details
(Keywords: perf, perf-alert, regression)
Perfherder has detected a browsertime performance regression from push da8fba53f7288360b026db54ea57ad9d0ca191fe. 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) |
|---|---|---|---|---|
| 3% | google-docs loadtime | macosx1015-64-shippable-qr | cold fission webrender | 785.58 -> 811.58 |
| 3% | google-docs SpeedIndex | macosx1015-64-shippable-qr | fission warm webrender | 943.92 -> 975.00 |
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 1773712
|
||
Updated•2 years ago
|
|
||
Comment 2•2 years ago
|
||
After looking in the profile, there is nothing really actionable that I didn't already address in bug 1783717. The regression here is small enough that if after landing 1783717 there is still any left over regression, I am okay with just leaving the regression in.
Description
•