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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgu92q_AoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg-5CmggoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg--jC5AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg-9P9tAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg-5GT9goM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgh_zJoQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgh4bBvgoM


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

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

Hi Minyue, it seems like this CL https://codereview.webrtc.org/2517243005 is causing a small perf regression. Could you have a look if this is expected?

The reason for the different test results is that no transport overhead is set. Which results in max packet size. 

This is intended.