Closed
Bug 1295490
Opened 8 years ago
Closed 8 years ago
2.87 - 8.29% damp (osx-10-10, windows7-32, windows8-64) regression on push 3d8a4df99f0ff5fab38afc6de0a678c043cf2ad4 (Thu Aug 11 2016)
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox48 | --- | unaffected |
firefox49 | --- | unaffected |
firefox50 | --- | unaffected |
firefox51 | --- | fixed |
People
(Reporter: ashiue, Unassigned)
References
Details
(Keywords: perf, regression, talos-regression)
Talos has detected a Firefox performance regression from push 3d8a4df99f0ff5fab38afc6de0a678c043cf2ad4. As author of one of the patches included in that push, we need your help to address this regression. Summary of tests that regressed: damp summary windows7-32 opt e10s: 271.06 -> 280.13 (3.35% worse) damp summary osx-10-10 opt e10s: 268.98 -> 276.7 (2.87% worse) damp summary windows7-32 pgo e10s: 200.52 -> 211.7 (5.58% worse) damp summary windows8-64 opt e10s: 259.35 -> 280.86 (8.29% worse) You can find links to graphs and comparison views for each of the above tests at: https://treeherder.mozilla.org/perf.html#/alerts?id=2485 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
Reporter | ||
Comment 1•8 years ago
|
||
This issue might be caused by one of following changesets: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=c9879bf9369e8410c0e44d8ca35565b76c99e7e4&tochange=3d8a4df99f0ff5fab38afc6de0a678c043cf2ad4 Hi Jon, as you are the patch author, can you take a look at this and determine what is the root cause? Thanks!
Blocks: 1291351
Flags: needinfo?(jcoppeard)
Comment 2•8 years ago
|
||
I've run the tests locally (on MacOS) before and after the changes, but I didn't see any significant differences. Continuing to investigate.
Updated•8 years ago
|
status-firefox48:
--- → unaffected
status-firefox49:
--- → unaffected
status-firefox50:
--- → unaffected
Comment 3•8 years ago
|
||
All of these tests seems to have returned to their original levels since the final backout of bug 1293239 on August 22nd.
Flags: needinfo?(jcoppeard)
Comment 4•8 years ago
|
||
I see that, shall we marked this as resolved->fixed?
Comment 5•8 years ago
|
||
Marking fixed.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Comment 6•8 years ago
|
||
Per comment #3 & 5, mark 51 as fixed.
You need to log in
before you can comment on or make changes to this bug.
Description
•