5.69% assorted-dom (Windows) regression on Thu June 16 2022
Categories
(Core :: JavaScript Engine: JIT, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox104 | --- | affected |
People
(Reporter: alexandrui, Unassigned)
References
(Regression)
Details
(Keywords: perf, perf-alert, regression)
Perfherder has detected a browsertime performance regression from push 103f879d45ff94ed79464af1fce977e54e6ac6e9. 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% | assorted-dom | windows10-64-shippable-qr | fission webrender | 19.43 -> 20.54 |
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.
Reporter | ||
Updated•3 years ago
|
Comment 1•3 years ago
|
||
Thanks for filing. Looking at the graph, this went back to normal, but it's possible the frame pointer changes made this go up and down a bit with particular changes. Random changes in cache lines and stack alignment often affect micro-benchmarks a lot unfortunately.
Description
•