Issue metadata
Sign in to add a comment
|
10.2%-40.9% regression in rendering.mobile/thread_raster_cpu_time_per_frame at 600933:601033 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Nov 7
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14674183e40000
,
Nov 7
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/14674183e40000 gpu: Fix raster implementation error for no flush result available query by khushalsagar@chromium.org https://chromium.googlesource.com/chromium/src/+/da82bcce69bf5384435976a1945c9cb3270c5abb thread_raster_cpu_time_per_frame: 5.549 → 7.919 (+2.37) Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: https://bit.ly/rendering-benchmarks
,
Nov 7
The regression is countering an improvement from a previous change that introduced an error this change fixed. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Nov 7