Issue metadata
Sign in to add a comment
|
7.2%-16% regression in system_health.memory_desktop at 580494:580696 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 8
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/148b0ffc640000
,
Aug 8
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/148b0ffc640000
,
Aug 8
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14a69c44640000
,
Aug 8
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/16d6ea10640000
,
Aug 8
it still looks like a real regression. let me run two other benchmarks
,
Aug 8
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/14a69c44640000 Scheduler: Extend resource fetch priority experiment to loading only. by farahcharab@google.com https://chromium.googlesource.com/chromium/src/+/bac05e51eb8937e213689a3e190acd697467eef6 1.705e+07 → 1.839e+07 (+1.334e+06) Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Aug 8
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/16d6ea10640000 Scheduler: Extend resource fetch priority experiment to loading only. by farahcharab@google.com https://chromium.googlesource.com/chromium/src/+/bac05e51eb8937e213689a3e190acd697467eef6 9.166e+06 → 1.023e+07 (+1.065e+06) Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Aug 8
,
Jan 11
Assigned, but no owner or component? Please find a component and/or owner |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 8