Issue metadata
Sign in to add a comment
|
5.5%-6.3% regression in system_health.common_desktop at 604709:604810 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Nov 8
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/11c8228be40000
,
Nov 8
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/11c8228be40000
,
Nov 9
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/12df824be40000
,
Nov 9
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/12df824be40000 Register fling scheduler on GSB instead of GFS. by sahel@chromium.org https://chromium.googlesource.com/chromium/src/+/0e58f2caab6a230fdb0f2b1993a44c2f4546c2f5 cpu_time_percentage: 0.1552 → 0.1624 (+0.007237) Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: https://bit.ly/system-health-benchmarks
,
Nov 9
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Nov 8