Cap probing bitrate to max total allocated bitrate

Bug: webrtc:10070
Change-Id: I3ba2656dff08e9ff054e263d78dcacba1ff77dd1
Reviewed-on: https://webrtc-review.googlesource.com/c/112384
Commit-Queue: Erik Språng <sprang@webrtc.org>
Reviewed-by: Sebastian Jansson <srte@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#25845}
This commit is contained in:
Erik Språng
2018-11-29 17:32:48 +01:00
committed by Commit Bot
parent 5976bde2e6
commit cfe36ca3b3
3 changed files with 51 additions and 6 deletions

View File

@ -102,7 +102,8 @@ class ProbeController {
int64_t bitrate_before_last_large_drop_bps_;
int64_t max_total_allocated_bitrate_;
bool in_rapid_recovery_experiment_;
const bool in_rapid_recovery_experiment_;
const bool limit_probes_with_allocateable_rate_;
// For WebRTC.BWE.MidCallProbing.* metric.
bool mid_call_probing_waiting_for_result_;
int64_t mid_call_probing_bitrate_bps_;