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

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


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

Android Nexus5 Perf
android-nexus5x-perf

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

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

Looks like noise.

📍 Found significant differences after each of 8 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/16904606540000

[protoc] Use protoc's lite java plugin and runtime by mheikal@chromium.org
https://chromium.googlesource.com/chromium/src/+/8aa669efad5cd46935c89fbd96dfe3d207d5ce9e
thread_raster_cpu_time_per_frame: 0.2098 → No values

Reland "[protoc] Use protoc's lite java plugin and runtime" by oysteine@chromium.org
https://chromium.googlesource.com/chromium/src/+/cabc7f418640412ae496bd23fdd096efac1f7b33
thread_raster_cpu_time_per_frame: No values → 0.2261

Reland "Perfetto: Stop splitting _COMPLETE events" by oysteine@google.com
https://chromium.googlesource.com/chromium/src/+/9d830c214cd1c59958ee19403b446fa5b796e794
thread_raster_cpu_time_per_frame: 0.2211 → 0.2058 (-0.01537)

Roll src/clank e4cd142554e2..e28e4df19610 (1 commits) by chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com
https://chrome-internal.googlesource.com/chrome/src-internal/+/2f6611fd011ff7e836ec014036e20c7e3807bf77
thread_raster_cpu_time_per_frame: 0.2044 → No values

Roll src/clank 40b1b2e50f8d..ebc8f3490109 (1 commits) by chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com
https://chrome-internal.googlesource.com/chrome/src-internal/+/6dc38ecea5d2f1857ba750f204143467f471231c
thread_raster_cpu_time_per_frame: No values → 0.2063

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

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.611 → 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.6128

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

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