All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=923366

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=0b522dd098c9b831fe08dc03f39e571d1163cd9b9cb78d1d131fe37dc9cc292c


Bot(s) for this bug's original alert(s):

android-nexus5x-perf

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/11cbd6d2540000

📍 Found significant differences after each of 3 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/11cbd6d2540000

Reland "perfetto: Enable SMB scraping" by eseckler@chromium.org
https://chromium.googlesource.com/chromium/src/+/884929d17a33fadadde7c772e08128e9191c56b6
thread_raster_cpu_time_per_frame: 0.4747 → 1.615 (+1.141)

Track when the auto-fetch in progress notification should be shown by harringtond@google.com
https://chromium.googlesource.com/chromium/src/+/0b15d057e7dacd7e14d2ff3b0308c1cc2b706695
thread_raster_cpu_time_per_frame: 1.613 → No values

Revert "Track when the auto-fetch in progress notification should be shown" by timvolodine@chromium.org
https://chromium.googlesource.com/chromium/src/+/dd6d6cf97b6a95c258cb7deb49b6a3ead32ddad1
thread_raster_cpu_time_per_frame: No values → 1.601

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks