Now probe for x3 and x6 the initial start bitrate.

Now probe for x3 and x6 of the initial start bitrate and allow for faster receive bitrates when calculating probing estimates.

BUG=webrtc:5859
Committed: https://crrev.com/4e7e8d73004eeb2e8b72fb546888b94fb00dea06
Cr-Commit-Position: refs/heads/master@{#13894}

[philipel, 2016-08-23 13:04:19]

Description was changed from

==========
Now probe for x3 and x6 the initial start bitrate.

BUG=webrtc:5859
==========

to

==========
Now probe for x3 and x6 of the initial start bitrate and allow for faster
receive bitrates when calculating probing estimates.

BUG=webrtc:5859
==========

[philipel, 2016-08-23 13:04:20]

philipel@webrtc.org changed reviewers:
+ stefan@webrtc.org

[philipel, 2016-08-23 13:07:50]

isheriff@:
The |initial_probing_triggered_| can be replaced by the |start_bitrate_bps_| in
your CL: https://codereview.webrtc.org/2269873002/
This is just a quick fix so we get this behavior with m54.

[stefan-webrtc, 2016-08-23 14:54:27]

https://codereview.webrtc.org/2269993002/diff/1/webrtc/modules/congestion_con...
File webrtc/modules/congestion_controller/congestion_controller.cc (right):

https://codereview.webrtc.org/2269993002/diff/1/webrtc/modules/congestion_con...
webrtc/modules/congestion_controller/congestion_controller.cc:233: if
(!initial_probing_triggered_  && start_bitrate_bps > 0) {
Can start_bitrate_bps be zero? That sounds strange.

https://codereview.webrtc.org/2269993002/diff/1/webrtc/modules/congestion_con...
webrtc/modules/congestion_controller/congestion_controller.cc:237: }
Should we add a test to ensure this doesn't regress?

[philipel, 2016-08-23 15:49:17]

https://codereview.webrtc.org/2269993002/diff/1/webrtc/modules/congestion_con...
File webrtc/modules/congestion_controller/congestion_controller.cc (right):

https://codereview.webrtc.org/2269993002/diff/1/webrtc/modules/congestion_con...
webrtc/modules/congestion_controller/congestion_controller.cc:233: if
(!initial_probing_triggered_  && start_bitrate_bps > 0) {
On 2016/08/23 14:54:27, stefan-webrtc (holmer) wrote:
> Can start_bitrate_bps be zero? That sounds strange.

It can't, fixed.

https://codereview.webrtc.org/2269993002/diff/1/webrtc/modules/congestion_con...
webrtc/modules/congestion_controller/congestion_controller.cc:237: }
On 2016/08/23 14:54:27, stefan-webrtc (holmer) wrote:
> Should we add a test to ensure this doesn't regress?

There are perf tests that react to these changes already.

[stefan-webrtc, 2016-08-23 15:49:47]

lgtm

[philipel, 2016-08-23 15:50:49]

The CQ bit was checked by philipel@webrtc.org

[commit-bot: I haz the power, 2016-08-23 15:50:56]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.webrtc.org/...

[commit-bot: I haz the power, 2016-08-23 17:51:39]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-08-23 17:51:40]

Try jobs failed on following builders:
  android_arm64_rel on master.tryserver.webrtc (JOB_TIMED_OUT, no build URL)

[philipel, 2016-08-24 10:47:07]

The CQ bit was checked by philipel@webrtc.org

[commit-bot: I haz the power, 2016-08-24 10:47:17]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.webrtc.org/...

[commit-bot: I haz the power, 2016-08-24 10:49:46]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-08-24 10:49:47]

Try jobs failed on following builders:
  presubmit on master.tryserver.webrtc (JOB_FAILED,
http://build.chromium.org/p/tryserver.webrtc/builders/presubmit/builds/7663)

[philipel, 2016-08-24 10:53:45]

The CQ bit was checked by philipel@webrtc.org

[philipel, 2016-08-24 10:53:46]

The patchset sent to the CQ was uploaded after l-g-t-m from stefan@webrtc.org
Link to the patchset: https://codereview.webrtc.org/2269993002/#ps40001 (title:
"Rebase")

[commit-bot: I haz the power, 2016-08-24 10:53:47]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.webrtc.org/...

[commit-bot: I haz the power, 2016-08-24 13:27:03]

Description was changed from

==========
Now probe for x3 and x6 of the initial start bitrate and allow for faster
receive bitrates when calculating probing estimates.

BUG=webrtc:5859
==========

to

==========
Now probe for x3 and x6 of the initial start bitrate and allow for faster
receive bitrates when calculating probing estimates.

BUG=webrtc:5859
==========

[commit-bot: I haz the power, 2016-08-24 13:27:06]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2016-08-24 13:27:08]

Description was changed from

==========
Now probe for x3 and x6 of the initial start bitrate and allow for faster
receive bitrates when calculating probing estimates.

BUG=webrtc:5859
==========

to

==========
Now probe for x3 and x6 of the initial start bitrate and allow for faster
receive bitrates when calculating probing estimates.

BUG=webrtc:5859

Committed: https://crrev.com/4e7e8d73004eeb2e8b72fb546888b94fb00dea06
Cr-Commit-Position: refs/heads/master@{#13894}
==========

[commit-bot: I haz the power, 2016-08-24 13:27:09]

Patchset 3 (id:??) landed as
https://crrev.com/4e7e8d73004eeb2e8b72fb546888b94fb00dea06
Cr-Commit-Position: refs/heads/master@{#13894}