2.81 - 3.88% tart (linux64, windows7-32) regression on push 2a1b0b22bfcd708dc89d21227ce5aa3a188e684e (Mon Aug 14 2017)




a year ago
a year ago


(Reporter: jmaher, Unassigned)


({perf, regression, talos-regression})

53 Branch
perf, regression, talos-regression
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)




a year ago
Talos 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.


  4%  tart summary linux64 opt e10s     5.57 -> 5.79
  4%  tart summary windows7-32 pgo e10s 4.83 -> 5.00
  3%  tart summary windows7-32 opt e10s 6.75 -> 6.96
  3%  tart summary linux64 pgo e10s     4.82 -> 4.96

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

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

Comment 1

a year ago
::dao, I see you are the patch author- looking at the bug it seems reasonable that we would see changes in the TART test, are these expected, or are there things you think we could do to get some performance back?
Flags: needinfo?(dao+bmo)

Comment 2

a year ago
::dao, any updates here?
I think this is just a cost we have to accept unless we want to regress bug 1388044.
Flags: needinfo?(dao+bmo)
Last Resolved: a year ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.