Issue metadata
Sign in to add a comment
|
1.3%-35.8% regression in rendering.desktop/tasks_per_frame_total_all at 604760:604825 |
||||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Nov 8
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/16e92f0de40000
,
Nov 8
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/16e92f0de40000
,
Nov 9
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/114a93e3e40000
,
Nov 10
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/114a93e3e40000 Perfetto: Fix for worker threads not finalizing proto packets by oysteine@google.com https://chromium.googlesource.com/chromium/src/+/d420ce980291dbdee3d8a68594afbbfe5b75fbb4 thread_total_all_cpu_time_per_frame: 8.089 → 8.572 (+0.4834) Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: https://bit.ly/rendering-benchmarks
,
Nov 27
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Nov 8