0.34 - 0.34% Base Content JS / Base Content JS (OSX) regression on Fri April 9 2021
Categories
(Core :: DOM: Device Interfaces, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr78 | --- | unaffected |
| firefox87 | --- | unaffected |
| firefox88 | --- | unaffected |
| firefox89 | --- | affected |
People
(Reporter: alexandrui, Unassigned)
References
(Regression)
Details
(Keywords: perf, perf-alert, regression)
Perfherder has detected a awsy performance regression from push 454b8e6f3a5d27ad6e92c17f523ddb4e18e03a0b. 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) |
|---|---|---|---|---|---|
| 0.34% | Base Content JS | macosx1015-64-shippable-qr | 2,408,288.00 -> 2,416,544.00 | ||
| 0.34% | Base Content JS | macosx1015-64-shippable-qr | 2,408,288.00 -> 2,416,544.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) 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
|
||
Hmm? I don't think the basic IDL addition can cause any perf regression, unless there is a hidden IDL layer issue. 🤔
Comment 2•4 years ago
•
|
||
Reverting it does restore it, which is mysterious to me. There could be potential perf bottleneck in IDL side, or not 🤷♀️
NI'ing :smaug for visibility.
Comment 3•4 years ago
|
||
Set release status flags based on info from the regressing bug 1697093
Comment 4•4 years ago
|
||
Okay, so it seems that we are at a boundary that adding more attributes doubles the dynamic slot. Since we are expected to add more and more attributes, this regression should be accepted.
Updated•4 years ago
|
Description
•