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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1JeAswoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtNyVqwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtI66swkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtI7VuwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtIDLtgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtI6hqgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtKrergkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1OXMqQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1OXauAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtJjJqgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtOy1twsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1OWwsAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1NGjqwoM


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

webrtc-android-tests-nexus5
webrtc-linux-large-tests
webrtc-win-large-tests

There are many affected perf stats that seem to be caused by this CL: https://codereview.webrtc.org/1947873002 . Some are improvements, but there are also many regressions. Per, could you have a look at this? 

It turns out that the failing tests is due to a bug in the current code that runs the proper at 300kbit regardless of configured start bitrate.
With https://codereview.webrtc.org/1958113003/ , the prober will run at the rate configured. 

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

commit ec81bcd5198cc09e4332ddeee195a1c992b6a780
Author: perkj <perkj@webrtc.org>
Date: Wed May 11 13:01:13 2016

Remove SendPacer from ViEEncoder and make sure SendPacer starts at a valid bitrate

This reverts commit e30c27205148b34ba421184efe65f6a0780b436d (https://codereview.webrtc.org/1958053002/)

Original reverted cl is in patch set #1.
Changes in following patch sets.

The cl now also make sure SendPacer starts with the configured bitrate provided in a call to CongestionController::SetBweBitrates)()

It turns out that the failing tests in 609816 is due to a bug in the current code that runs the proper at 300kbit regardless of configured start bitrate.

Original cl description:
Remove SendPacer from ViEEncoder
This CL moves the logic where the ViEEncoder pause if the pacer is full to the BitrateController. If the queue is full, the controller reports a bitrate of zero to  Call (and BitrateAllocator)

BUG= chromium:609816 ,  webrtc:5687 
TBR=mflodman@webrtc.org
NOTRY=True  // Due to bug  in android_x86 cq builder....

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

[modify] https://crrev.com/ec81bcd5198cc09e4332ddeee195a1c992b6a780/webrtc/audio/audio_receive_stream_unittest.cc
[modify] https://crrev.com/ec81bcd5198cc09e4332ddeee195a1c992b6a780/webrtc/audio/audio_send_stream_unittest.cc
[modify] https://crrev.com/ec81bcd5198cc09e4332ddeee195a1c992b6a780/webrtc/call/bitrate_allocator.cc
[modify] https://crrev.com/ec81bcd5198cc09e4332ddeee195a1c992b6a780/webrtc/call/bitrate_allocator.h
[modify] https://crrev.com/ec81bcd5198cc09e4332ddeee195a1c992b6a780/webrtc/call/bitrate_allocator_unittest.cc
[modify] https://crrev.com/ec81bcd5198cc09e4332ddeee195a1c992b6a780/webrtc/call/call.cc
[modify] https://crrev.com/ec81bcd5198cc09e4332ddeee195a1c992b6a780/webrtc/modules/bitrate_controller/bitrate_controller_impl.cc
[modify] https://crrev.com/ec81bcd5198cc09e4332ddeee195a1c992b6a780/webrtc/modules/bitrate_controller/bitrate_controller_impl.h
[modify] https://crrev.com/ec81bcd5198cc09e4332ddeee195a1c992b6a780/webrtc/modules/bitrate_controller/bitrate_controller_unittest.cc
[modify] https://crrev.com/ec81bcd5198cc09e4332ddeee195a1c992b6a780/webrtc/modules/bitrate_controller/include/bitrate_controller.h
[modify] https://crrev.com/ec81bcd5198cc09e4332ddeee195a1c992b6a780/webrtc/modules/bitrate_controller/include/mock/mock_bitrate_controller.h
[modify] https://crrev.com/ec81bcd5198cc09e4332ddeee195a1c992b6a780/webrtc/modules/congestion_controller/congestion_controller.cc
[add] https://crrev.com/ec81bcd5198cc09e4332ddeee195a1c992b6a780/webrtc/modules/congestion_controller/congestion_controller_unittest.cc
[modify] https://crrev.com/ec81bcd5198cc09e4332ddeee195a1c992b6a780/webrtc/modules/congestion_controller/include/congestion_controller.h
[modify] https://crrev.com/ec81bcd5198cc09e4332ddeee195a1c992b6a780/webrtc/modules/congestion_controller/include/mock/mock_congestion_controller.h
[modify] https://crrev.com/ec81bcd5198cc09e4332ddeee195a1c992b6a780/webrtc/modules/modules.gyp
[modify] https://crrev.com/ec81bcd5198cc09e4332ddeee195a1c992b6a780/webrtc/modules/pacing/mock/mock_paced_sender.h
[modify] https://crrev.com/ec81bcd5198cc09e4332ddeee195a1c992b6a780/webrtc/modules/pacing/paced_sender.cc
[modify] https://crrev.com/ec81bcd5198cc09e4332ddeee195a1c992b6a780/webrtc/modules/pacing/paced_sender.h
[modify] https://crrev.com/ec81bcd5198cc09e4332ddeee195a1c992b6a780/webrtc/modules/pacing/paced_sender_unittest.cc
[modify] https://crrev.com/ec81bcd5198cc09e4332ddeee195a1c992b6a780/webrtc/modules/pacing/packet_router.h
[modify] https://crrev.com/ec81bcd5198cc09e4332ddeee195a1c992b6a780/webrtc/modules/remote_bitrate_estimator/remote_bitrate_estimator.gypi
[modify] https://crrev.com/ec81bcd5198cc09e4332ddeee195a1c992b6a780/webrtc/modules/remote_bitrate_estimator/test/estimators/send_side.h
[modify] https://crrev.com/ec81bcd5198cc09e4332ddeee195a1c992b6a780/webrtc/modules/remote_bitrate_estimator/test/packet_sender.cc
[modify] https://crrev.com/ec81bcd5198cc09e4332ddeee195a1c992b6a780/webrtc/modules/remote_bitrate_estimator/test/packet_sender.h
[modify] https://crrev.com/ec81bcd5198cc09e4332ddeee195a1c992b6a780/webrtc/video/encoder_state_feedback_unittest.cc
[modify] https://crrev.com/ec81bcd5198cc09e4332ddeee195a1c992b6a780/webrtc/video/video_send_stream.cc
[modify] https://crrev.com/ec81bcd5198cc09e4332ddeee195a1c992b6a780/webrtc/video/vie_encoder.cc
[modify] https://crrev.com/ec81bcd5198cc09e4332ddeee195a1c992b6a780/webrtc/video/vie_encoder.h

Great, thanks Per!

The expected alerts fired again after the reland in #6 and I associated them with this bug.