2.3 - 0.25% Base Content Resident Unique Memory / Base Content JS + 2 more (Linux, OSX, Windows) regression on Wed June 26 2024
Categories
(Testing :: Performance, defect)
Tracking
(Not tracked)
People
(Reporter: bacasandrei, Unassigned)
Details
(Keywords: perf, perf-alert, regression)
Perfherder has detected a awsy performance regression from push e705ed34801dff9e254260b3a517b6c6087da0b8. As author of one of the patches included in that push, we need your help to address this regression.
Improvements:
| Ratio | Test | Platform | Options | Absolute values (old vs new) |
|---|---|---|---|---|
| 2% | Base Content Resident Unique Memory | windows11-64-2009-shippable-qr | fission | 10,865,066.67 -> 10,615,466.67 |
| 0.25% | Base Content JS | linux1804-64-shippable-qr | fission | 1,511,866.67 -> 1,508,074.67 |
| 0.25% | Base Content JS | macosx1015-64-shippable-qr | fission | 1,513,320.00 -> 1,509,480.00 |
| 0.25% | Base Content JS | windows11-64-2009-shippable-qr | fission | 1,518,339.50 -> 1,514,520.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.
If you need the profiling jobs you can trigger them yourself from treeherder job view or ask a sheriff to do that for you.
You can run these tests on try with ./mach try perf --alert 1179
For more information on performance sheriffing please see our FAQ.
|
Reporter | |
Updated•1 year ago
|
|
|
Reporter | |
Updated•1 year ago
|
Description
•