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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICggpr6vgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICggvOisQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICggo35sQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICggsm6tgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICggonnqwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_I3OsgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICggrPzrwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICggrOVtgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICggomDsgoM


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

webrtc-android-tests-nexus5
webrtc-android-tests-nexus9
webrtc-linux-large-tests
webrtc-mac-large-tests
webrtc-win-large-tests

Hi Danil, your recent CL (https://codereview.webrtc.org/2046943004) made a change to the way some perf stats are calculated. Could you check if the change in the stats is what you expected?

Yes, it is expected and desired: it was fixing  issue 618226 

Great, thanks.