29 - 2.32% damp custom.netmonitor.close.DAMP / netmonitor-metrics + 5 more (Linux, OSX, Windows) regression on Fri February 7 2025
Categories
(DevTools :: Netmonitor, defect)
Tracking
(firefox-esr128 unaffected, firefox135 unaffected, firefox136 unaffected, firefox137 affected)
Tracking | Status | |
---|---|---|
firefox-esr128 | --- | unaffected |
firefox135 | --- | unaffected |
firefox136 | --- | unaffected |
firefox137 | --- | affected |
People
(Reporter: intermittent-bug-filer, Unassigned)
References
(Blocks 1 open bug, Regression)
Details
(4 keywords)
Perfherder has detected a devtools performance regression from push e9742b2e36d928f3a76c3ff215b4dda8b3ca1e12. 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) |
---|---|---|---|---|
29% | damp custom.netmonitor.close.DAMP | macosx1470-64-shippable | e10s fission stylo webrender | 20.41 -> 26.32 |
5% | damp custom.netmonitor.bigdatarequests.requestsFinished.DAMP | windows11-64-shippable-qr | e10s fission stylo webrender | 1,081.21 -> 1,138.43 |
5% | damp custom.netmonitor.manyrequests.requestsFinished.DAMP | macosx1470-64-shippable | e10s fission stylo webrender | 2,483.51 -> 2,596.92 |
4% | damp custom.netmonitor.bigdatarequests.navigate.DAMP | windows11-64-shippable-qr | e10s fission stylo webrender | 980.31 -> 1,019.08 |
3% | damp custom.netmonitor.manyrequests.requestsFinished.DAMP | linux1804-64-shippable-qr | e10s fission stylo webrender | 2,899.47 -> 2,991.00 |
3% | damp custom.netmonitor.manyrequests.requestsFinished.DAMP | windows11-64-shippable-qr | e10s fission stylo webrender | 1,285.13 -> 1,324.55 |
2% | netmonitor-metrics | linux1804-64-qr | 3,503,377.00 -> 3,584,483.00 |
Improvements:
Ratio | Test | Platform | Options | Absolute values (old vs new) |
---|---|---|---|---|
3% | damp simple.netmonitor.close.DAMP | windows11-64-shippable-qr | e10s fission stylo webrender | 4.49 -> 4.34 |
3% | netmonitor-metrics | linux1804-64-qr | 3,614,661.46 -> 3,523,653.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 43788
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 fbilt@mozilla.com.
Comment 1•10 days ago
|
||
Set release status flags based on info from the regressing bug 1849920
Comment 2•10 days ago
|
||
Overall the regression is not too surprising, there is slightly more complexity to display the requests list, but I will still try to see if one patch in particular is responsible for the regression.
Comment 3•2 days ago
|
||
It has been over 7 days with no activity on this performance regression.
:jdescottes, since you are the author of the regressor, bug 1849920, which triggered this performance alert, could you please provide a progress update?
If this regression is something that fixes a bug, changes the baseline of the regression metrics, or otherwise will not be fixed, please consider closing it as WONTFIX. See this documentation for more information on how to handle regressions.
For additional information/help, please needinfo the performance sheriff who filed this alert (they can be found in comment #0), or reach out in #perftest, or #perfsheriffs on Element.
For more information, please visit BugBot documentation.
Comment 4•2 days ago
|
||
Ok well I'm closing as WONTFIX and filing another bug to investigate.
Description
•