Issue metadata
Sign in to add a comment
|
13.2%-13.4% regression in system_health.memory_desktop at 585104:585143 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 24
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14ddccb6640000
,
Aug 24
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/14ddccb6640000 Turn on OOP Raster on mac bots by enne@chromium.org https://chromium.googlesource.com/chromium/src/+/ee35f329c8e615505326a3b4df9ae4b7764037ae 8.66e+06 → 9.708e+06 (+1.048e+06) Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Aug 28
,
Aug 28
,
Aug 29
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/1707480d640000
,
Aug 29
I think this regression is a WontFix. Its in memory reported by v8 which should definitely be unaffected by this change. There is a 1M increase in large_object_spaces under heap_spaces. The only explanation I can think of is a possible timing change in when blink_gc runs now..?
,
Aug 29
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/1707480d640000 Turn on OOP Raster on mac bots by enne@chromium.org https://chromium.googlesource.com/chromium/src/+/ee35f329c8e615505326a3b4df9ae4b7764037ae 8.651e+06 → 9.814e+06 (+1.163e+06) Understanding performance regressions: http://g.co/ChromePerformanceRegressions |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 24