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

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


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

linux

Assigning to sheriff gbiv@chromium.org because this autoroll is the only CL in range:
Roll AFDO from 69.0.3472.0_rc-r1 to 69.0.3473.0_rc-r1

This CL may cause a small binary size increase, roughly proportional
to how long it's been since our last AFDO profile roll. For larger
increases (around or exceeding 100KB), please file a bug against
gbiv@chromium.org. Additional context:  https://crbug.com/805539 

The AutoRoll server is located here: https://afdo-chromium-roll.skia.org

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=gbiv@chromium.org

Change-Id: I49e0b9d21a920a916e3335a38d5871c1cb131c59
Reviewed-on: https://chromium-review.googlesource.com/1114476
Commit-Queue: afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#570361}

0.4% is more than what I'd expect for an AFDO roll, but it looks like the roll from 3448 to 3449 saved us 0.4%, and the roll from 3350 to 3372 saved us another 0.1%, (rolls were disabled between 3350 and 3372, due to  issue 851539 ) so I'm attributing this to noise.

Noise investigations (both perf and size) are being tracked in issue 849881.