0.43 - 0.42% Base Content JS / Base Content JS + 1 more (Linux, OSX, Windows) regression on Wed February 15 2023
Categories
(Core :: JavaScript: GC, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox112 | --- | wontfix |
People
(Reporter: bacasandrei, Unassigned)
References
(Regression)
Details
(Keywords: perf, perf-alert, regression)
Perfherder has detected a awsy performance regression from push 20c40d607f5ac4abaf9f617381d1f902434a616d. 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.43% | Base Content JS | linux1804-64-shippable-qr | fission | 1,642,430.86 -> 1,649,433.33 |
| 0.43% | Base Content JS | windows10-64-2004-shippable-qr | fission | 1,649,048.00 -> 1,656,057.33 |
| 0.42% | Base Content JS | macosx1015-64-shippable-qr | fission | 1,646,801.60 -> 1,653,769.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
|
||
This is reporting memory that wasn't reported before, so there's no actual change. I imagine there was a corresponding reduction when bug 1786506 landed.
Updated•2 years ago
|
Description
•