0.29 - 0.26% Base Content JS / Base Content JS + 2 more (Linux, OSX, Windows) regression on Thu September 8 2022
Categories
(Web Compatibility :: Interventions, defect)
Tracking
(firefox-esr91 unaffected, firefox-esr102 unaffected, firefox104 unaffected, firefox105 unaffected, firefox106 wontfix, firefox107 wontfix)
Tracking | Status | |
---|---|---|
firefox-esr91 | --- | unaffected |
firefox-esr102 | --- | unaffected |
firefox104 | --- | unaffected |
firefox105 | --- | unaffected |
firefox106 | --- | wontfix |
firefox107 | --- | wontfix |
People
(Reporter: bacasandrei, Unassigned)
References
(Regression)
Details
(Keywords: perf, perf-alert, regression)
Perfherder has detected a awsy performance regression from push 80e0a6e2b5ecfc8eedcaffae8e2a9863295d561b. 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) |
---|---|---|---|---|
0.29% | Base Content JS | linux1804-64-shippable-qr | fission | 1,606,577.33 -> 1,611,168.67 |
0.27% | Base Content JS | windows10-64-2004-shippable-qr | fission | 1,611,942.00 -> 1,616,310.00 |
0.27% | Base Content JS | macosx1015-64-shippable-qr | fission | 1,606,289.33 -> 1,610,605.33 |
0.26% | Base Content JS | macosx1015-64-shippable-qr | fission | 1,606,292.67 -> 1,610,413.33 |
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 1776675
Comment 2•2 years ago
|
||
Set release status flags based on info from the regressing bug 1776675
Comment 3•2 years ago
|
||
I'm not entirely convinced that this is caused by the addon change. The patch in question added a few interventions and removed a few interventions, but there was no change to the global JS. Looking at the future development of that graph, it sometimes bumps up and down with roughly the same value.
Looking at other pushes in the same area, I noticed bug 1341937, which probably could have an impact here. However, since the change is so low and appears to be within the usual fluctuations, I'll close this as wontfix for now.
Updated•2 years ago
|
Description
•