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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2ujargsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDguoiFuQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2obp6AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2oXeuAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2o_DugsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2ujargkM


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

webrtc-mac-large-tests

The commit in question is: https://chromium.googlesource.com/external/webrtc/+/7f52f084219fdd8003ff0312b81a2a991ad5f572

The same thing happened to webrtc in  bug 721761 .

I don't think that CL could have caused any improvement because the generated binaries should be the same

Added more alerts.

Yes, this is revert of regressions caused by chromium roll at commit: https://chromium.googlesource.com/external/webrtc/+/210cb8d656918a0f70f3fadc3c5b4c9d49624af0
which is addressed at  bug 721761 .

As this commit could not cause such improvements in any senseful way.