Issue metadata
Sign in to add a comment
|
3.5% regression in rendering.mobile/thread_total_all_cpu_time_per_frame at 594393:594468 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Oct 2
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/145cb828e40000
,
Oct 2
📍 Found significant differences after each of 2 commits. https://pinpoint-dot-chromeperf.appspot.com/job/145cb828e40000 Define basic Trichrome build targets. by torne@google.com https://chromium.googlesource.com/chromium/src/+/bef92b9197b49def215aced79961f50e3b83544e 18.86 → No values Revert "Define basic Trichrome build targets." by thomasanderson@chromium.org https://chromium.googlesource.com/chromium/src/+/f505cde61a75f566b4edd2043015a93e5568f970 No values → 19.52 Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: https://bit.ly/rendering-benchmarks
,
Oct 2
,
Oct 23
Looks like just mostly noise to me. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Oct 2