2.73 - 5.5% raptor-tp6-apple-firefox / raptor-tp6-apple-firefox fcp (windows10-64, windows10-64-qr, windows7-32) regression on push 00df850ac3cf71777ed07daef849fc3f16d51fd5 (Thu Feb 14 2019)
Categories
(Testing :: Raptor, defect)
Tracking
(Not tracked)
People
(Reporter: igoldan, Unassigned)
References
Details
(Keywords: perf, regression)
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:
6% raptor-tp6-apple-firefox fcp windows10-64 opt 302.48 -> 319.12
4% raptor-tp6-apple-firefox windows7-32 opt 407.92 -> 425.23
4% raptor-tp6-apple-firefox windows10-64 opt 411.64 -> 428.32
3% raptor-tp6-apple-firefox windows10-64-qr opt 408.77 -> 419.94
You can find links to graphs and comparison views for each of the above tests at: https://treeherder.mozilla.org/perf.html#/alerts?id=19370
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 | ||
Comment 1•6 years ago
|
||
Seems like this has updated our Raptor baselines on Windows. Given it's just a harness update, I'd conclude this as wontfix.
:rwood are you ok with this?
Comment 2•6 years ago
|
||
I wouldn't expect this change to cause any regressions as we're using the same version of mitmproxy. If there was a regression I would expect it to affect all tp6 tests on Windows.
Comment 3•6 years ago
|
||
This also seems a bit odd to me. :bebe, can you please look into this? Do you think somehow using the different mimtproxy binary (even though it's the same version) could cause playback for this one site to regress?
Comment 4•6 years ago
|
||
I don't know why we get that regression on apple.
If it would be a mitmproxy issue I would expect this to be visible on all tests.
But this regression is only on apple.com
Comment 5•6 years ago
|
||
As the only change here was a change to the harness/tools let's accept this regression.
Reporter | ||
Updated•6 years ago
|
Description
•