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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8MjetgoM


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

webrtc-android-tests-nexus5-kitkat

brandtr@: This regression seems to possibly be related to your CL https://codereview.webrtc.org/2646343005. Could you please take a look?

I don't think it's related, as that CL only reorders some member function declarations/definitions.

Are the alerts only on the Android bots? My experience is that their numbers can be quite noisy. Maybe the two "modes" in the rampdown test can be explained by two different devices running the same test?

holmer: You are more familiar with the RampUp tests. Any idea if this alert is reason for concern?

It seems to be a lot worse, but your explanation could be correct.

If it's only visible on this device I guess we could ignore it, it does look like it happened every now and then before too.

I didn't see any other suspicious webrtc change in the nearby datapoints either...

I think it looks too stable to be explained by noise but I have not seen any other such regressions.

Would you consider the amount of increase as being so high that we should be concerned with it?

Removing R-V-G label (was set upon bug filing because the bot was incorrectly configured as internal)

holmer@: Would you consider the amount of increase as being so high that we should be concerned with it?

I think we can ignore it. Probably caused by some change in timing.