Closed Bug 1412809 Opened 3 years ago Closed 3 years ago

3.26% damp (linux64) regression on push 53f5585bb94d (Fri Oct 27 2017)


(Firefox :: Theme, defect)

Not set



Tracking Status
firefox57 --- unaffected


(Reporter: igoldan, Unassigned)



(Keywords: perf, regression, talos-regression)

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.


  3%  damp summary linux64 opt e10s     268.04 -> 276.78

You can find links to graphs and comparison views for each of the above tests at:

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:

For information on reproducing and debugging the regression, either on try or locally, see:

*** 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:
Component: Untriaged → Theme
:jaws This regressions only appears on Linux's OPT builds, but not on PGO builds. It's kind of strange and situations like these happen once and a while. Could you give a reason why bug 1406414 could cause a perf regression?
Flags: needinfo?(jaws)
It is possible that the OPT builds are triggering the "schedule-pressure" condition and the PGO builds are not (since they should be running some amount faster). When the "schedule-pressure" condition is met, we change how we draw our loading/progress throbbers, and that switch-over would be the cause of the regression.
Flags: needinfo?(jaws)
So, wontfix?
Flags: needinfo?(jaws)
Correct, yeah we should resolve this as WONTFIX.
Closed: 3 years ago
Flags: needinfo?(jaws)
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.