Closed Bug 1391741 Opened 7 years ago Closed 7 years ago

2.95% tcanvasmark (windows7-32) regression on push 397fe94c67f12877fd4b7136388a2708689e2de2 (Wed Aug 16 2017)

Categories

(Firefox :: Pocket, defect)

53 Branch
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: jmaher, Unassigned)

References

Details

(Keywords: perf, regression, talos-regression)

Talos has detected a Firefox performance regression from push:

https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=397fe94c67f12877fd4b7136388a2708689e2de2

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

Regressions:

  3%  tcanvasmark summary windows7-32 pgo e10s     9,754.57 -> 9,466.46


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

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
:adw, I see you authored the patch which looks to have caused this regression.  Luckily this looks to be tcanvasmark only and pgo specific (not on opt).  can you take a look at this and see if there is something that might be related to your code that could cause a tcanvasmark regression?

p.s. as a note, if this is pgo only, it could be a side effect of the pgo process.
Flags: needinfo?(adw)
(In reply to Drew Willcoxon :adw from bug 1385418 comment #23)
> It seems impossible for this bug to have regressed *canvas* performance. 
> This is purely a front-end bug and there's no way it could have impacted any
> part of the core web platform, like canvas.
Flags: needinfo?(adw)
thanks :adw, :snorp, you had originally asked for canvasmark to run, do you agree with this?  should we assume this is a pgo side effect?
Flags: needinfo?(snorp)
I'm fine with assuming it's a PGO side effect.
Flags: needinfo?(snorp)
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.