3.36% google-docs PerceptualSpeedIndex (OSX) regression on Thu August 31 2023
Categories
(Core :: Graphics: Text, defect, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr102 | --- | unaffected |
| firefox-esr115 | --- | unaffected |
| firefox117 | --- | unaffected |
| firefox118 | --- | unaffected |
| firefox119 | + | wontfix |
People
(Reporter: aesanu, Unassigned)
References
(Regression)
Details
(Keywords: perf, perf-alert, regression)
Perfherder has detected a browsertime performance regression from push 42ff0ef2bc5dc19a26e4ed7050f383575f3b5785. 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 |
|---|---|---|---|---|---|
| 8% | google-docs ContentfulSpeedIndex | macosx1015-64-shippable-qr | fission warm webrender | 865.82 -> 937.40 | Before/After |
| 7% | google-docs ContentfulSpeedIndex | macosx1015-64-shippable-qr | cold fission webrender | 1,187.12 -> 1,265.64 | Before/After |
| 3% | google-docs PerceptualSpeedIndex | macosx1015-64-shippable-qr | fission warm webrender | 745.74 -> 770.78 | 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 1170986
Updated•2 years ago
|
Updated•2 years ago
|
Comment 2•2 years ago
|
||
The bug is marked as tracked for firefox119 (nightly). We have limited time to fix this, the soft freeze is in 10 days. However, the bug still isn't assigned.
:bhood, could you please find an assignee for this tracked bug? Given that it is a regression and we know the cause, we could also simply backout the regressor. If you disagree with the tracking decision, please talk with the release managers.
For more information, please visit BugBot documentation.
Comment 3•2 years ago
|
||
Updated•2 years ago
|
Updated•2 years ago
|
Description
•