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

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


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/14ab18bc540000

📍 Found significant differences after each of 4 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/14ab18bc540000

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

[Media Foundation Video Capture] Enable by default by chfremer@chromium.org
https://chromium.googlesource.com/chromium/src/+/c4f58b3898a92a0f7001f45415acf215b6481c65
thread_raster_cpu_time_per_frame: 0.9701 → 0.8711 (-0.09893)

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: 0.8711 → 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 → 0.8834

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

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