Talos has detected a Firefox performance regression from push:

https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?changeset=581eed270cffaf9c19285ce97029aa5516123829

As author of one of the patches included in that push, we need your help to address this regression.

Regressions:

21% glterrain windows10-64-pgo-qr opt e10s stylo 0.80 -> 0.97

You can find links to graphs and comparison views for each of the above tests at: https://treeherder.mozilla.org/perf.html#/alerts?id=19889

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 Talos jobs in a pushlog format.

To learn more about the regressing test(s), please see: https://wiki.mozilla.org/Performance_sheriffing/Talos/Tests

For information on reproducing and debugging the regression, either on try or locally, see: https://wiki.mozilla.org/Performance_sheriffing/Talos/Running

*** 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

It is an expected regression by Bug 1531294. As in Bug 1531294 Comment 25, previous glterrain score was wrong.

Also noticed a Raptor benchmark regression on Windows 10 QR:

== Change summary for alert #19881 (as of Wed, 13 Mar 2019 01:31:04 GMT) ==

Regressions:

3% raptor-motionmark-animometer-firefox windows10-64-pgo-qr opt 42.98 -> 41.65

For up to date results, see: https://treeherder.mozilla.org/perf.html#/alerts?id=19881

The regression in Comment 2 is also expected since the benchmark improvement was also got by Bug 1526213 as in Bug 1526213 Comment 12.