Issue metadata
Sign in to add a comment
|
11.3% regression in blink_perf.parser at 620247:620266 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jan 10
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/15e12dbd940000
,
Jan 19
(4 days ago)
📍 Found significant differences after each of 2 commits. https://pinpoint-dot-chromeperf.appspot.com/job/15e12dbd940000 DocumentParser should not rely on dummy AppendBytes call by dgozman@chromium.org https://chromium.googlesource.com/chromium/src/+/4f3f51a479aba7cd77531ad7b655abd22f92cd7a html-parser-threaded: 5.682e+04 → 5.752e+04 (+699.7) Revert https://crrev.com/c/1148172 to control the HTML parser yield by fergal@chromium.org https://chromium.googlesource.com/chromium/src/+/2d7da2e9289a81e9ba92ba54af8887cdc20e7fd4 html-parser-threaded: 5.742e+04 → 6.186e+04 (+4439) Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: https://bit.ly/blink-perf-benchmarks |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jan 10