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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg7PuCuAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg7JqdvgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgnNCGpAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg7ITqtQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg7POeoAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg7I3wugoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg7L6HrQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg7MTYqgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgnNCcuQoM


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

webrtc-android-tests-nexus5
webrtc-android-tests-nexus72
webrtc-win-large-tests

I assume minyue intended to assign to nisse@

I have some difficulty understanding if/how my cl could cause this. It could affect the use of cpu and memory, but I guess the graphs shows an increase in packets on the wire? That is a bit puzzling, maybe if someone could explain what's really being measured?

I'm trying to review my bug list. But I have little clue what's happening for this one. The way I read the graphs, the number of packets on the wire is changed by my cl, commit number 12919. Which makes no sense to me.

Any suggestion on how to proceed?

Closing, I see no reasonable action to take on this old issue.