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

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


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

Android Nexus6 WebView Perf

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

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

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

trace writer: Send patches after completing fragmented packet by eseckler@google.com
https://android.googlesource.com/platform/external/perfetto/+/15697965801191b657fa3213139ff8532b2e6cc7
thread_raster_cpu_time_per_frame: 6.275e-05 → 0.0005168 (+0.0004541)

perfetto: fix tracing test on Android ASAN by lalitm@google.com
https://android.googlesource.com/platform/external/perfetto/+/39236f3b69dd2700fb9c3bde74e7432c23bc9f15
thread_raster_cpu_time_per_frame: 0.0005168 → 0.0001065 (-0.0004103)

trace writer: Send patches after completing fragmented packet by eseckler@google.com
https://android.googlesource.com/platform/external/perfetto/+/15697965801191b657fa3213139ff8532b2e6cc7
thread_raster_cpu_time_per_frame: 0.0001712 → 0.0005168 (+0.0003456)

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

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