2.91 - 0.93% compiler_metrics num_static_constructors / compiler_metrics num_static_constructors + 1 more (Windows) regression on Wed October 20 2021
Categories
(Core :: Graphics: CanvasWebGL, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox-esr91 | --- | unaffected |
firefox93 | --- | unaffected |
firefox94 | --- | unaffected |
firefox95 | --- | affected |
People
(Reporter: aesanu, Unassigned)
References
(Regression)
Details
(Keywords: perf-alert, regression)
Perfherder has detected a build_metrics performance regression from push 27ceffd9709134a53810f97a45b75f3a1f83ef1a. 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) |
---|---|---|---|---|
3% | compiler_metrics num_static_constructors | windows2012-aarch64 | aarch64-no-eme | 106.40 -> 109.50 |
2% | compiler_metrics num_static_constructors | windows2012-aarch64 | aarch64-no-eme | 106.75 -> 109.17 |
1% | compiler_metrics num_static_constructors | windows2012-aarch64 | aarch64-no-eme | 107.00 -> 108.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•3 years ago
|
||
Set release status flags based on info from the regressing bug 1735431
Comment 2•3 years ago
|
||
Is it possible this is due to the whims of the optimizer?
I believe this was an entirely mechanical change, combining source files. Though these were already part of unified builds, the order of them may have changed.
I don't think I made any non-trivial changes other than moving code around.
I would like to WONTFIX this.
Updated•3 years ago
|
Updated•3 years ago
|
Description
•