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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgqN_aswsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6OWJrwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6NXbtwoM


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

webrtc-win-large-tests

I don't think it is my CL because it was already reverted and the issue persists. I suspect https://chromium.googlesource.com/external/webrtc/+/2bc6864278d74e88711f62b4a735d6e7af4dc4dd because it has caused perf problems previously.

I think it's very likely that this is my CL. It's logical that it would cause a delay increase.

So, is it WAI?

The following revision refers to this bug:
  https://chromium.googlesource.com/external/webrtc.git/+/ad9010c983631356bef481a2fc609b152a4e1410

commit ad9010c983631356bef481a2fc609b152a4e1410
Author: kthelgason <kthelgason@webrtc.org>
Date: Tue Feb 14 08:46:51 2017

Make sure initial framedrop is off where quality scaling is off.

BUG= chromium:689972 ,chromium:689915

Review-Url: https://codereview.webrtc.org/2684683004
Cr-Commit-Position: refs/heads/master@{#16602}

[modify] https://crrev.com/ad9010c983631356bef481a2fc609b152a4e1410/webrtc/video/vie_encoder.cc
[modify] https://crrev.com/ad9010c983631356bef481a2fc609b152a4e1410/webrtc/video/vie_encoder_unittest.cc

I take it it was fixed in commit #16602? If you agree, it would make sense to link the corresponding bumps on the graphs to this bug too.

Thanks for the suggestion Nisse, will do.