Issue metadata
Sign in to add a comment
|
1.6%-∞% regression in avg_surface_fps,frame_times,percentage_smooth,tasks_per_frame_total_all,thread_raster_cpu_time_per_frame,thread_total_all_cpu_time_per_frame at 603899:604528 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Nov 2
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/13f594a1e40000
,
Nov 2
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/13f594a1e40000 Perfetto: Fix for worker threads not finalizing proto packets by oysteine@google.com https://chromium.googlesource.com/chromium/src/+/d420ce980291dbdee3d8a68594afbbfe5b75fbb4 thread_raster_cpu_time_per_frame: 0 → 0.02602 (+0.02602) Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: https://bit.ly/rendering-benchmarks
,
Nov 2
,
Nov 9
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/12b7c887e40000
,
Dec 11
Issue 903176 has been merged into this issue. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Nov 2