Issue metadata
Sign in to add a comment
|
1.8%-83.2% regression in system_health.memory_desktop at 552586:552591 |
||||||||||||||||||||||
Issue descriptionIs this from --site-per-process?
,
Apr 24 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14869419c40000
,
Apr 24 2018
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/14869419c40000 Make --site-per-process the default on ToT via fieldtrial_testing_config by lukasza@chromium.org https://chromium.googlesource.com/chromium/src/+/fb1ccf02ee8ca79e1404abfd3a3a7d540b7d2dbd Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Apr 24 2018
It is expected that site-per-process uses more memory - on average we expect to increase memory usage (e.g. as measured by Memory.Total.PrivateMemoryFootprint) by around 10%.
,
May 2 2018
,
May 2 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Apr 24 2018