0.31 - 0.3% Base Content JS / Base Content JS + 2 more (Linux, OSX, Windows) regression on Fri January 13 2023
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox109 | --- | unaffected |
firefox110 | --- | wontfix |
firefox111 | --- | wontfix |
People
(Reporter: bacasandrei, Unassigned)
References
(Regression)
Details
(Keywords: perf, perf-alert, regression)
Perfherder has detected a awsy performance regression from push f2457a464d0333448b4f53e5b768653a83d9701a. 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.31% | Base Content JS | linux1804-64-shippable-qr | fission | 1,618,264.00 -> 1,623,320.67 |
0.30% | Base Content JS | macosx1015-64-shippable-qr | fission | 1,622,168.00 -> 1,627,064.00 |
0.30% | Base Content JS | windows10-64-2004-shippable-qr | fission | 1,626,128.00 -> 1,630,976.00 |
0.30% | Base Content JS | macosx1015-64-shippable-qr | fission | 1,622,168.00 -> 1,627,064.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•1 year ago
|
||
bug 1807228 patch reverts the change done by bug 1805149 patch, and bug 1805149 patch and others improved the score by 0.3%.
So this regression is expected and nothing gets regressed compared to before bug 1805149 patch.
re-landing the bug 1807228 patch with other performance fix will re-improve the score again.
Updated•1 year ago
|
Description
•