12.7% perf_reftest_singletons style-attr-1.html (Windows) regression on Thu April 14 2022
Categories
(Core :: CSS Parsing and Computation, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr91 | --- | unaffected |
| firefox99 | --- | unaffected |
| firefox100 | --- | unaffected |
| firefox101 | --- | affected |
People
(Reporter: aglavic, Unassigned)
References
(Regression)
Details
(4 keywords)
Perfherder has detected a talos performance regression from push ba7c9f270e1938870ac35d8c901f6c1132972a13. 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) |
|---|---|---|---|---|
| 13% | perf_reftest_singletons style-attr-1.html | windows10-64-shippable-qr | e10s fission stylo webrender | 2.80 -> 3.16 |
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.
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•3 years ago
|
||
Set release status flags based on info from the regressing bug 1764217
|
|
||
Updated•3 years ago
|
|
||
Comment 2•3 years ago
|
||
Looking at the graph this is not terribly concerning I think, it seems to have gone mostly back to recent values.
Given this is a micro-benchmark prone to subtle changes to compiler optimizations, I think it's not worth spending a lot of time on it, but lmk if you disagree. The test is supposed to test that an optimization that would make it orders of magnitude slower still works.
Description
•