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

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


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

Android Nexus6 WebView Perf

blink_perf.canvas - Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks

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

Splitting this out from issue 877184 - bisect pointed to:

Roll AFDO from 70.0.3529.0_rc-r1 to 70.0.3530.0_rc-r1 by afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/9f547654633778c99e48754b772b75d088f6280a
672.5 → 545.6 (-126.9)

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/109bdf13640000

Roll AFDO from 70.0.3529.0_rc-r1 to 70.0.3530.0_rc-r1 by afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/9f547654633778c99e48754b772b75d088f6280a
668.2 → 546.1 (-122)

Assigning to sheriff gbiv@chromium.org because "Roll AFDO from 70.0.3529.0_rc-r1 to 70.0.3530.0_rc-r1" is a roll.

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

I'm assuming this'll go the same as  issue 877606 , but we don't appear to have data since the 24th, so :(

I'll keep an eye on the chart for new data, in any case.

Thanks!

Appears to be recovered and reasonably stable (though depending on how issue 889742 goes, we may still disable AFDO for this benchmark).