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

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


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

Android Nexus5 Perf
Android Nexus5X WebView Perf
Android Nexus6 WebView Perf
linux-perf

rasterize_and_record_micro.top_25 - Benchmark documentation link:
  None

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/131f9a47640000

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

Roll AFDO from 71.0.3554.0_rc-r1 to 71.0.3555.0_rc-r1 by afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/4b8803051fc24556622b6c8532a7b7ba73f64a8d
6.185 → 9.901 (+3.716)

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

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

Benchmark documentation link:
  None

Interesting. The nexus6 webview perf bot might still be slightly regressed after the 3556 roll. The data points are within the upper-bound of the pre-regression noise, but I'll keep this open as reminder to look again probably early next week.

With that out of the way, incoming copy-paste ;)

At this point, I've received five perf bugs for this single 3555 profile roll, all of which have recovered with the 3556 roll.

It's rare (< monthly), but we will occasionally have a profile that's just way off. I'll look into whether there's any obvious reason for this particular flake (we use Chrome ToT; if that crashes or glitches out a benchmark, or profile gets really skewed), but given that everything's back to normal and there's ~no signal we can realistically get from these flakes, ...

Hopefully our swap to field-focused profiles (Q4 maybe?) will make this issue go away, but only time will tell.

Added a note of this all in the denoising bug, issue 849881.