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

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


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/15a6a732e40000

📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/15a6a732e40000

converted AARectEffect to new FP system by ethannicholas@google.com
https://skia.googlesource.com/skia/+/222e275b0ab4c8a2af152c637bf9dbc28b4a097f
thread_raster_cpu_time_per_frame: 0.977 → 1.356 (+0.3791)

Roll src/third_party/skia 9c37cd96e4c8..3655e4059e1f (61 commits) by chromium-autoroll@skia-public.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/a198424ee0993d0344994ebaab2efdc48bbc2847
thread_raster_cpu_time_per_frame: 1.352 → 1.241 (-0.1107)

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

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