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

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


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

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

[IdentityManager] Access PO2TS synchronously for getting accounts by blundell@chromium.org
https://chromium.googlesource.com/chromium/src/+/ad9d4c2b86d8b307d3a9d791a522ec10d191bfde
79.91 → 78.13 (-1.779)

Revert "Reland "Enable Perfetto by default for all telemetry tests"" by pasko@chromium.org
https://chromium.googlesource.com/chromium/src/+/f36de8b1bdc40bf31455b052ef63338072b093da
78.13 → 119.1 (+40.96)

Avoid calls to GetAllNodes() while datatype is NOT_RUNNING by treib@chromium.org
https://chromium.googlesource.com/chromium/src/+/1f55f08837aeff172cd891dd1b39f2315dfc896d
118.8 → 117.6 (-1.279)

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

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