2.99 - 10.36% raptor-tp6 (linux64, windows10-64) regression on push 3cddc7cd4da5fcd26b93becb55a028621ab68f64 (Fri Mar 8 2019)
Categories
(Core :: DOM: Security, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox-esr68 | --- | wontfix |
firefox67 | --- | wontfix |
firefox68 | --- | wontfix |
firefox69 | --- | fixed |
People
(Reporter: igoldan, Assigned: baku)
References
Details
(Keywords: perf, perf-alert, regression, Whiteboard: [domsecurity-active])
Attachments
(2 files)
Raptor has detected a Firefox performance regression from push:
As author of one of the patches included in that push, we need your help to address this regression.
Regressions:
10% raptor-tp6-microsoft-firefox fcp windows10-64 pgo 482.17 -> 532.12
10% raptor-tp6-wikia-firefox linux64 pgo 164.93 -> 181.44
5% raptor-tp6-wikia-firefox loadtime linux64 pgo 183.94 -> 192.29
5% raptor-tp6-imdb-firefox loadtime linux64 pgo 522.06 -> 545.62
4% raptor-tp6-imgur-firefox fcp linux64 pgo 271.75 -> 281.92
3% raptor-tp6-amazon-firefox fcp windows10-64 pgo 255.77 -> 264.54
3% raptor-tp6-imgur-firefox linux64 pgo 294.21 -> 303.02
Improvements:
6% raptor-assorted-dom-firefox linux64 pgo 26.69 -> 25.10
You can find links to graphs and comparison views for each of the above tests at: https://treeherder.mozilla.org/perf.html#/alerts?id=19829
On the page above you can see an alert for each affected platform as well as a link to a graph showing the history of scores for this test. There is also a link to a Treeherder page showing the Raptor jobs in a pushlog format.
To learn more about the regressing test(s) or reproducing them, please see: https://wiki.mozilla.org/Performance_sheriffing/Raptor
*** Please let us know your plans within 3 business days, or the offending patch(es) will be backed out! ***
Our wiki page outlines the common responses and expectations: https://wiki.mozilla.org/Performance_sheriffing/Talos/RegressionBugsHandling
Reporter | ||
Updated•6 years ago
|
Reporter | ||
Updated•6 years ago
|
Reporter | ||
Comment 1•6 years ago
|
||
These are the Gecko profiles for tp6-amazon on Windows 10 (PGO builds):
For tp6-wikia on Linux 64bit (PGO builds):
Assignee | ||
Comment 2•6 years ago
|
||
I'm debugging this regression. I'll tell you more about the time range for the fix for today, max tomorrow.
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Comment 3•6 years ago
|
||
Updated•6 years ago
|
Comment 5•6 years ago
|
||
bugherder |
Reporter | ||
Comment 6•6 years ago
|
||
I'm afraid push from comment 4 didn't fix the regressions. I only saw a partial fix on raptor-tp6-amazon-firefox fcp windows10-64-pgo-qr, but the other baselines remained unchanged.
Updated•6 years ago
|
Assignee | ||
Updated•6 years ago
|
Reporter | ||
Comment 7•6 years ago
|
||
I also noticed a fix for raptor-tp6-microsoft-firefox fcp linux64 pgo:
== Change summary for alert #19948 (as of Mon, 18 Mar 2019 06:58:24 GMT) ==
Improvements:
4% raptor-tp6-microsoft-firefox fcp linux64 pgo 511.06 -> 488.92
For up to date results, see: https://treeherder.mozilla.org/perf.html#/alerts?id=19948
Reporter | ||
Comment 8•6 years ago
|
||
This is the Compare view for the new patch Andrea is working on. Keeping it here for easy reference.
Assignee | ||
Comment 9•6 years ago
|
||
Assignee | ||
Updated•6 years ago
|
Comment 10•6 years ago
|
||
Comment 11•6 years ago
|
||
bugherder |
Reporter | ||
Comment 12•6 years ago
|
||
Push from comment 10 still didn't fix the perf regressions. All of them remained the same.
There's lots of noise, especially after March 29, which makes the changes even more difficult to identify.
Assignee | ||
Comment 13•6 years ago
|
||
Can you tell me the % of regression after comment 10?
Reporter | ||
Comment 14•6 years ago
|
||
(In reply to Andrea Marchesini [:baku] from comment #13)
Can you tell me the % of regression after comment 10?
Yes, but you'll have to wait a bit so I can do some retriggers to obtain that percentage.
Reporter | ||
Comment 15•6 years ago
|
||
I've done the retriggers. In 3 ours I should have enough data to reply back.
Reporter | ||
Comment 16•6 years ago
•
|
||
I looked over the retriggers and and it's difficult to precisely state in percentages how much we've fixed.
The noise & big harness update around March 29 (which should mix into the equation) hide the small gains.
Comment 17•6 years ago
|
||
Marking as wontfix for 67 as we are not sure that the performance regressions would be addressed by the patches in this bug and we are in the middle of the nightly cycle already.
Assignee | ||
Comment 18•6 years ago
|
||
I did some improvements lately: bug 1554527 (not landed yet) and 1553867. Would be great if we can check if we still have regressions.
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Reporter | ||
Updated•5 years ago
|
Updated•5 years ago
|
Description
•