Issue metadata
Sign in to add a comment
|
3.4% regression in system_health.memory_desktop at 592380:592522 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Oct 2
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/11952752e40000
,
Oct 2
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/11952752e40000
,
Oct 4
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/167cb42ce40000
,
Oct 6
😿 Pinpoint job stopped with an error. https://pinpoint-dot-chromeperf.appspot.com/job/167cb42ce40000 The swarming task expired. The bots are likely overloaded, dead, or misconfigured.
,
Oct 8
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/17e61488e40000
,
Oct 9
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/17e61488e40000 Turn on full masking with untrusted-code-mitigations by jarin@chromium.org https://chromium.googlesource.com/v8/v8/+/6a6f050e18b90d5b498d85455e598ca68b14238f memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size: 6.026e+07 → 6.078e+07 (+5.225e+05) Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: https://bit.ly/system-health-benchmarks
,
Oct 9
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Oct 2