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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgiseLtgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgyoOZuAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgyuSN-ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgiv-xvAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgyuSN-goM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgyoit-AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgqpnjowoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgyuu2qwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgqvqqvAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgqqqktAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgyrLX8ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgyvnvrAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgiveAvgsM


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

webrtc-mac-large-tests

Yes, it would suggest 13479 or thereabouts is guilty. 

https://chromium.googlesource.com/external/webrtc/+/73ab917d27b6e66f075802c473cdec3d605ef5e5 doesn't seem very likely like you say. However, https://chromium.googlesource.com/external/webrtc/+/39607c9e3433389db0256d1df4fcdf58a99fedf8 (the CL before) changes mac code and the above regression is mac-only. That is very interesting.

Also https://chromium.googlesource.com/external/webrtc/+/6c4d0f0bbf2522b7869f6238a08e27535a5adcb1 is pretty close.

Danil, can you look up the owner of the test from blame info and ask them what the regressed numbers mean? Magnus, Henrik, cc:ing you since it's your CLs I mention above.

Per, this performance values are all about new Level Controller you added recently. Can you describe what their regression mean.

My CL is platform agnostic and only adds periodic logs once every 10 seconds. Can't be related IMO.

@peah, gentle ping. Any insights on this?

I cannot see anything changing in the code that warrants this increase. Has there been any changes in the hardware running the tests?

These are actually fine, since the tests do not yet do anything on Android. They will be resolved once the Android functionality is activated in the tests.