Issue metadata
Sign in to add a comment
|
14.8% regression in blink_perf.canvas at 534400:534464 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Feb 12 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/12c7368d840000
,
Feb 14 2018
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/12c7368d840000 Configure TaskScheduler to use one less worker than cores by default. by gab@chromium.org https://chromium.googlesource.com/chromium/src/+/f61636f214c9a53a91906a2ec4b35af511bb5b57 Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Feb 19 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/168374fb840000
,
Feb 19 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14d6e597840000
,
Feb 19 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/148a87e7840000
,
Feb 19 2018
This is the same as issue 809961 . The graphs appear to have recovered with chromium r536207 here as well (launched a few more bisects to confirm).
,
Feb 20 2018
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/168374fb840000 Fix 'num cores' in ConcurrentMarking as well. by gab@chromium.org https://chromium.googlesource.com/v8/v8/+/8996e262cc880d6d12ac7dc468964e6313fde023 Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Feb 21 2018
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Feb 12 2018