Talos has detected a Firefox performance regression from push: https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=f37162b6183944f2e38ab82651377cd83b038288 As author of one of the patches included in that push, we need your help to address this regression. Regressions: 4% sessionrestore_no_auto_restore windows10-64 pgo e10s 441.04 -> 458.67 4% ts_paint_webext windows10-64 pgo e10s 546.67 -> 567.83 4% sessionrestore windows10-64 pgo e10s 376.17 -> 390.58 4% ts_paint windows10-64 pgo e10s 486.54 -> 505.17 You can find links to graphs and comparison views for each of the above tests at: https://treeherder.mozilla.org/perf.html#/alerts?id=11437 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/Buildbot/Talos/Tests For information on reproducing and debugging the regression, either on try or locally, see: https://wiki.mozilla.org/Buildbot/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/Buildbot/Talos/RegressionBugsHandling
Component: Untriaged → Crash Reporting
Product: Firefox → Toolkit
:aklotz It looks like these regressions relate to bug 1430857, because the push-backout-push again pattern shows up on the performance graphs. I did some retriggers and will properly confirm this. Can you please take a look over the bug in question. Is there something we can do to fix it or should we accept it/back it out?
I don't want to do a full backout, but I will land a change to temporarily disable the problematic code.
https://hg.mozilla.org/integration/mozilla-inbound/rev/5472cdf7d7446b2f4b89906ddf092260c4d99e6c Bug 1436684: Disable cert annotation due to perf regressions; r=backout
You need to log in before you can comment on or make changes to this bug.