6.16 - 6.12% compiler_metrics num_static_constructors / compiler_metrics num_static_constructors (Windows) regression on Thu April 25 2024
Categories
(Core :: Audio/Video, defect, P5)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox125 | --- | unaffected |
| firefox126 | --- | unaffected |
| firefox127 | --- | fix-optional |
People
(Reporter: afinder, Unassigned)
References
(Regression)
Details
(Keywords: perf-alert, regression)
Perfherder has detected a build_metrics performance regression from push 399ca207b66fa17a2b093b420be369286c774f1d. 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) |
|---|---|---|---|---|
| 6% | compiler_metrics num_static_constructors | windows-mingw32 | 32 clang debug | 146.00 -> 155.00 |
| 6% | compiler_metrics num_static_constructors | windows-mingw32 | 64 clang debug | 147.00 -> 156.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 patch(es) may be backed out in accordance with our regression policy.
You can run these tests on try with ./mach try perf --alert 3
For more information on performance sheriffing please see our FAQ.
|
||
Comment 1•7 months ago
|
||
Set release status flags based on info from the regressing bug 1885671
|
||
Comment 2•7 months ago
|
||
Any guidance for this kind of regression? I always feel confused about this type of regression.
|
||
Updated•6 months ago
|
|
||
Updated•6 months ago
|
|
Reporter | |
Comment 3•6 months ago
|
||
(In reply to Alastor Wu [:alwu] from comment #2)
Any guidance for this kind of regression? I always feel confused about this type of regression.
Hi Alastor! Not sure on what the investigation for this type of regression defect would entail, but I'm assuming that analyzing the differences between the Profiler results for the job running on the culprit commit and comparing it to the Profiler results for the job that executed before that could provide some more information. Additionally, you can reach out on the Performance Tests and Build matrix channels for suggestions on how to investigate this defect further.
Description
•