Issue metadata
Sign in to add a comment
|
287.5% regression in system_health.memory_mobile at 533472:533605 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Feb 6 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/169fd091840000
,
Feb 7 2018
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/169fd091840000
,
Mar 6 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/11dca57c440000
,
Mar 6 2018
Some of the alerts recovered, but not all. Trying a bisect on a different metric.
,
Mar 7 2018
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/11dca57c440000 Move initCommandLine() to attachBaseContext (take 2) by agrieve@chromium.org https://chromium.googlesource.com/chromium/src/+/7ee6c14b661b0abdfb91f8f0c8a07c34f1d353bc Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Mar 7 2018
Not sure what to make of this. Very unlikely that this change affected memory usage. Especially not by 300%.
,
Mar 7 2018
could it shift the time when the memory dump is made?
,
Mar 26 2018
Looks like the memory graph recovered after a few runs: https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICQjJHYoAkM |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Feb 6 2018