Issue metadata
Sign in to add a comment
|
12.5% regression in blink_perf.canvas at 588439:588442 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 5
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/16fee5f5640000
,
Sep 6
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/16fee5f5640000 [turbofan] Be more consistent about Smi comparisons. by bmeurer@chromium.org https://chromium.googlesource.com/v8/v8/+/0aac3884c9e02b34861d526d2d5c62f8628483f3 888.7 → 788.2 (-100.5) Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: https://bit.ly/blink-perf-benchmarks
,
Sep 7
This is a micro-benchmark where the previous heuristics seems to be beneficial. Still better to be consistent here. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Sep 5