24.23 - 2.27% speedometer AngularJS-TodoMVC/Adding100Items/Sync / speedometer AngularJS-TodoMVC/DeletingAllItems + 8 more (OSX) regression on Fri March 28 2025
Categories
(Core :: Widget, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr128 | --- | unaffected |
firefox137 | --- | unaffected |
firefox138 | --- | wontfix |
firefox139 | --- | wontfix |
People
(Reporter: intermittent-bug-filer, Unassigned)
References
(Regression)
Details
(Keywords: perf, perf-alert, regression)
Perfherder has detected a browsertime performance regression from push 5217704a3449304f7b38bd3800bbcc04a52c01f7. As author of one of the patches included in that push, we need your help to address this regression.
Please acknowledge, and begin investigating this alert within 3 business days, or the patch(es) may be backed out in accordance with our regression policy. Our guide to handling regression bugs has information about how you can proceed with this investigation.
If you have any questions or need any help with the investigation, please reach out to fbilt@mozilla.com. Alternatively, you can find help on Slack by joining #perf-help, and on Matrix you can find help by joining #perftest.
Regressions:
Ratio | Test | Platform | Options | Absolute values (old vs new) | Performance Profiles |
---|---|---|---|---|---|
24% | speedometer AngularJS-TodoMVC/Adding100Items/Sync | macosx1400-64-shippable-qr | fission webrender | 35.04 -> 43.53 | Before/After |
23% | speedometer AngularJS-TodoMVC/Adding100Items | macosx1400-64-shippable-qr | fission webrender | 37.79 -> 46.55 | Before/After |
13% | speedometer AngularJS-TodoMVC | macosx1400-64-shippable-qr | fission webrender | 77.20 -> 87.57 | Before/After |
11% | speedometer AngularJS-TodoMVC/CompletingAllItems/Sync | macosx1400-64-shippable-qr | fission webrender | 13.31 -> 14.73 | Before/After |
10% | speedometer AngularJS-TodoMVC/CompletingAllItems | macosx1400-64-shippable-qr | fission webrender | 14.18 -> 15.61 | Before/After |
8% | speedometer AngularJS-TodoMVC/Adding100Items/Async | macosx1400-64-shippable-qr | fission webrender | 2.79 -> 3.01 | Before/After |
5% | speedometer EmberJS-TodoMVC/Adding100Items/Async | macosx1400-64-shippable-qr | fission webrender | 1.31 -> 1.38 | Before/After |
3% | speedometer | macosx1400-64-shippable-qr | fission webrender | 509.75 -> 496.56 | Before/After |
2% | speedometer AngularJS-TodoMVC/DeletingAllItems/Sync | macosx1400-64-shippable-qr | fission webrender | 22.34 -> 22.89 | Before/After |
2% | speedometer AngularJS-TodoMVC/DeletingAllItems | macosx1400-64-shippable-qr | fission webrender | 24.55 -> 25.11 | Before/After |
Details of the alert can be found in the alert summary, including links to graphs and comparisons for each of the affected tests.
If you need the profiling jobs you can trigger them yourself from treeherder job view or ask fbilt@mozilla.com to do that for you.
You can run all of these tests on try with ./mach try perf --alert 44677
The following documentation link provides more information about this command.
Comment 1•9 days ago
|
||
Set release status flags based on info from the regressing bug 1953907
Comment 2•9 days ago
|
||
I'm not sure what I'm looking at here... It seems there was a regression but then it went back to baseline? Are the improvements from bug 1955591 comment 10? Or something else?
Comment 3•8 days ago
|
||
Indeed, it returned to baseline but without generating an improvement alert.
Bug 1955591 mentioned by you above cannot be because it was landed before this patch.
If it help, I think I could find out which revision caused the return to baseline.
Comment 5•8 days ago
|
||
marking as wontfix but waiting on confirmation on what fix it/caused it.
Comment 6•7 days ago
|
||
Take a look here
https://treeherder.mozilla.org/perfherder/graphs?highlightAlerts=1&highlightChangelogData=1&highlightCommonAlerts=0&replicates=0&series=autoland,5041984,1,13&timerange=2592000&zoom=1743113416807,1743120441259,62.11259851974802,103.70190162336547
It seems like it was just a spike on that revision (not sure why).
I also triggered some re-runs on revisions where the regression seems to have started, and the new values appear to align with the new trend (baseline), which indicated an infra-related behaviour.
However, this doesn't explain the spike on this revision (5217704a3449304f7b38bd3800bbcc04a52c01f7).
Feel free to close this ticket as WONTFIX.
Comment 7•7 days ago
|
||
Thanks see comment 6. That revision had a bug that was fixed right after.
Description
•