2.96 - 2.45% imdb fcp / imdb fcp (Android) regression on Wed April 7 2021
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox87 | --- | unaffected |
firefox88 | --- | unaffected |
firefox89 | --- | affected |
People
(Reporter: Bebe, Unassigned)
References
(Regression)
Details
(Keywords: perf, perf-alert, regression)
Perfherder has detected a browsertime performance regression from push b00dca6a499518027381e5ae68926c0afa5ac7c4. As author of one of the patches included in that push, we need your help to address this regression.
Regressions:
Ratio | Suite | Test | Platform | Options | Absolute values (old vs new) |
---|---|---|---|---|---|
3% | imdb | fcp | android-hw-g5-7-0-arm7-api-16-shippable-qr | warm webrender | 564.94 -> 581.67 |
2% | imdb | fcp | android-hw-g5-7-0-arm7-api-16-shippable-qr | warm webrender | 562.71 -> 576.50 |
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) will be backed out in accordance with our regression policy.
For more information on performance sheriffing please see our FAQ.
Comment 1•4 years ago
|
||
Set release status flags based on info from the regressing bug 1700052
Comment 2•4 years ago
|
||
Thanks for reporting this!
This could be caused by changes in GC timing or so. I think we have to accept this one, the patches that landed unblock larger architectural changes we want to make the coming weeks/months that should improve both performance and memory usage (see bug 1704430).
Updated•4 years ago
|
Description
•