Issue metadata
Sign in to add a comment
|
1.3%-2.2% regression in system_health.memory_desktop at 545055:545153 |
||||||||||||||||||||
Issue descriptionNote that significant improvements were found at the same range: https://chromeperf.appspot.com/group_report?sid=a9ee828e59f75f97520cfc70ca8b8c0b4e32c19c699f42b0115c156365439f88 When a culprit is found, we should consider whether it is a net positive.
,
Mar 25 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/148f49e3440000
,
Mar 25 2018
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/148f49e3440000 Correct macOS private memory footprint calculations. by erikchen@chromium.org https://chromium.googlesource.com/chromium/src/+/7c1d03f55ec7a248aece22abfdef25e100bcf4f4 Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Mar 30 2018
WAI - this was an accounting change. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Mar 25 2018