Issue metadata
Sign in to add a comment
|
3.3%-115.5% regression in avg_surface_fps,frame_times,mean_frame_time,mean_frame_time_renderer_compositor,mean_input_event_latency,mean_main_thread_scroll_latency,percentage_smooth,tasks_per_frame_total_all,thread_raster_cpu_time_per_frame,thread_total_all_cpu_time_per_frame at 576404:583986 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 20
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/16f8d31a640000
,
Aug 25
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/16f8d31a640000 [PE] Stop dirtying compositing inputs on any layout for the root PaintLayer. by chrishtr@chromium.org https://chromium.googlesource.com/chromium/src/+/46520ae13478333fe882e79041b667e5a3112796 0.07206 → 0.151 (+0.07894) Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Aug 27
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 20