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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrKaKuwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgzKPL6AoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrObRuAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrOSzxQgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgzPK3oAsM


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

webrtc-android-tests-nexus5-kitkat

The values in the graphs go back to match the ones before this commit:

https://chromium.googlesource.com/external/webrtc/trunk/webrtc/+/b1d925831e11d33319a0b5bc4bd51703fa4b0c56

That CL has nothing to do with the values, and both that (which caused the values to increase) and this CL (that caused the values to go back down) look like no-ops, so it feels like something outside of this has changed.