∞% regression in tasks_per_frame_total_all,thread_raster_cpu_time_per_frame,thread_total_all_cpu_time_per_frame at 604976:605886 |
|||
Issue descriptionSee the link to graphs below.
,
Nov 21
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/11c95997e40000
,
Nov 21
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/11c95997e40000 Telemetry: finally move rendering to TBMv2 by chiniforooshan@chromium.org https://chromium.googlesource.com/chromium/src/+/05af02c8afe6a0fdc3d5e32ff88632fa15f5c567 tasks_per_frame_total_all: 0 → No values Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: https://bit.ly/rendering-benchmarks
,
Jan 11
Setting defect without priority to default. |
|||
►
Sign in to add a comment |
|||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Nov 21