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

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


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

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

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

system_health.memory_mobile - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks

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

memory.top_10_mobile - Benchmark documentation link:
  None

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/15eb742e640000

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

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
145.1 → 146.7 (+1.65)

[NTP] Fix floating ripple effect by kristipark@chromium.org
https://chromium.googlesource.com/chromium/src/+/562e9ac32b7e4f8d827dd215ae7ab172a6780f06
147.6 → No values

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

(I'm only seeing the blink regression on the pinpoint charts. Please let me know if there's a memory regression I'm missing. https://chromeperf.appspot.com/group_report?bug_id=877600 is saying "no data available", despite being logged in with my @chromium account)

Will keep an eye on this to see if a later AFDO roll fixes it. In general, blink_perf.* benchmarks can be quite sensitive to individual optimization decisions by the compiler. Since our AFDO profiles heavily influence the optimization decisions that our compiler makes, it's expected to see some afdo-induced noise occasionally.

Thanks!

Hmm...I get the "no data available" error too. Sounds like there's nothing actionable on this bug, so closing it. Feel free to re-open if I'm wrong here.