8.62 - 7.33% cpstartup content-process-startup / cpstartup content-process-startup (Linux) regression on Thu October 31 2024
Categories
(Core :: Internationalization, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr128 | --- | unaffected |
| firefox132 | --- | unaffected |
| firefox133 | --- | unaffected |
| firefox134 | --- | affected |
People
(Reporter: intermittent-bug-filer, Unassigned)
References
(Regression)
Details
(4 keywords)
Perfherder has detected a talos performance regression from push 6d6ee1c2471701a7ecc056d807cbbff12bd7fb8e. 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) |
|---|---|---|---|---|
| 9% | cpstartup content-process-startup | linux1804-64-shippable-qr | e10s fission stylo webrender | 51.71 -> 56.17 |
| 7% | cpstartup content-process-startup | linux1804-64-shippable-qr | e10s fission stylo webrender | 51.71 -> 55.50 |
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 all of these tests on try with ./mach try perf --alert 42545
The following documentation link provides more information about this command.
For more information on performance sheriffing please see our FAQ.
If you have any questions, please do not hesitate to reach out to aglavic@mozilla.com.
|
||
Comment 1•1 year ago
|
||
Set release status flags based on info from the regressing bug 1927706
|
||
Comment 2•1 year ago
|
||
Unfortunately we likely have to accept this regression, because we shouldn't keep deferring the update to a more recent ICU. Otherwise we run into cross-browser compatibility issues (e.g. bug 1909112 or bug 1919905) and we run behind in sec-updates (e.g. 1871635, 1871636, 1871623).
Description
•