Issue metadata
Sign in to add a comment
|
thread_times.tough_compositor_cases reporting 0 |
||||||||||||||||||||||||
Issue descriptionThese graphs have recently been reporting 0 for thread cpu_time metrics. e.g.: https://chromeperf.appspot.com/report?sid=cf1064f9eb008917991a7947c5b8a0a3abbd2c255dd86397156032d4d38343ec&start_rev=542767&end_rev=543699
,
Mar 16 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/17cdc989440000
,
Mar 17 2018
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/17cdc989440000 [scheduler] Use WorkerSchedulerProxy in DedicatedWorkerThread. by altimin@chromium.org https://chromium.googlesource.com/chromium/src/+/053b619cf7ac1dd0ed6504e6e65da0e45d0a9d4e Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Mar 19 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by bokan@chromium.org
, Mar 16 2018