Closed Bug 1291349 Opened 4 years ago Closed 4 years ago
.91 - 13 .28% tp5o Private Bytes (linux64) regression on push 9cdec67ac091 (Mon Aug 1 2016)
Talos has detected a Firefox performance regression from push 9cdec67ac091. As author of one of the patches included in that push, we need your help to address this regression. Summary of tests that regressed: tp5o Private Bytes linux64 opt - 8.91% worse tp5o Private Bytes linux64 opt e10s - 11.8% worse tp5o Private Bytes linux64 pgo - 9.89% worse tp5o Private Bytes linux64 pgo e10s - 13.28% 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=2198 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
there are a lot of patches which landed at the same time, all the same author/reviewer- I assume we don't need bisection, but if we do, please let us know! :fitzgen, can you look into this? I am verifying there are no other regressions, but so far we see linux64 private bytes regression on all configs (opt, pgo, e10s)
Hi! I was on vacation, but I'm back now. Looking into this
Joel, I'm 95% sure that bug 1290287 is the actual regression, but can you double check that via bisection? I don't want to start digging in too deep into the wrong thing. Thanks!
After some digging into what is actually being measured here and correlating these results with the RSS measurements, I think we can safely WONTFIX. On linux, the private size is the size of the address space that we have reserved, regardless whether those pages actually get physically allocated. In contrast, RSS includes only the physically allocated pages. As you can see in this graph, RSS is flat across this jump in private bytes. That means that we are now reserving more of the address space, but we aren't actually allocating any more physical memory. This is slightly interesting, but not worrying.  https://treeherder.mozilla.org/perf.html#/graphs?series=%5Bautoland,28190da32789550c38b066e9802290bf53031500,1,1%5D&series=%5Bfx-team,28190da32789550c38b066e9802290bf53031500,1,1%5D&series=%5Bmozilla-inbound,28190da32789550c38b066e9802290bf53031500,1,1%5D&series=%5Bmozilla-inbound,28125e4ebe8be696adbb5e1f591c1f003ef927b4,1,1%5D&series=%5Bmozilla-inbound,efaf2e61e0a0296500286dcb1a895d301705cfe0,1,1%5D&series=%5Bmozilla-inbound,7611104f6070472709426e321be354a6de3f18d3,1,1%5D&series=%5Bmozilla-inbound,8423e4e61246ad0fd04a998dfb924c75192efd11,1,1%5D
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
thanks for looking into this Nick- the initial bisection had a problem on try and we were going to try again in a while- this saves more try pushes!
You need to log in before you can comment on or make changes to this bug.