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

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


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

Android Nexus5 Perf
Android Nexus6 WebView Perf
android-nexus5x-perf

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

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

Roll AFDO from 70.0.3508.3_rc-r1 to 70.0.3510.3_rc-r1 by afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/f54ac12a5462e5c68b5dc1974d3f0bf02c8c4860
88.95 → 64.14 (-24.81)

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

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

Hello again :)

Same story (and pattern) as  issue 872169 . On the bright side, it looks like the most recent roll put us back at the pre-regression levels. Hopefully that'll stick...