Refactor use of ProbeController::OnMaxTotalAllocatedBitrate
Instead of disabling probing when the total allocated bitrate has changed in goog_cc, it can be done via a new field trial parameter, "probe_max_allocation". Not that the currently used flag RateControlSettings::TriggerProbeOnMaxAllocatedBitrateChange() is per default enabled and will be cleaned up in a follow up cl. The field trial flag "skip_if_est_larger_than_fraction_of_max" now also skip probing if the current estimate is larger than the currently max allocated bitrate. ie, alr probing is skippe if the current estimate > max configured bitrate or current estimate > max send bitrate of all streams. Bug: webrtc:14392 Change-Id: I2a09be39f85a9122410edd5acb1158ece12fca60 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/282860 Reviewed-by: Diep Bui <diepbp@webrtc.org> Commit-Queue: Per Kjellander <perkj@webrtc.org> Cr-Commit-Position: refs/heads/main@{#38597}
This commit is contained in:
committed by
WebRTC LUCI CQ
parent
f1fa7058b6
commit
01e8a2ad7c
@ -62,6 +62,7 @@ struct ProbeControllerConfig {
|
||||
FieldTrialParameter<TimeDelta> network_state_probe_duration;
|
||||
|
||||
// Configures the probes emitted by changed to the allocated bitrate.
|
||||
FieldTrialParameter<bool> probe_on_max_allocated_bitrate_change;
|
||||
FieldTrialOptional<double> first_allocation_probe_scale;
|
||||
FieldTrialOptional<double> second_allocation_probe_scale;
|
||||
FieldTrialFlag allocation_allow_further_probing;
|
||||
@ -119,8 +120,6 @@ class ProbeController {
|
||||
ABSL_MUST_USE_RESULT std::vector<ProbeClusterConfig> RequestProbe(
|
||||
Timestamp at_time);
|
||||
|
||||
// Sets a new maximum probing bitrate, without generating a new probe cluster.
|
||||
void SetMaxBitrate(DataRate max_bitrate);
|
||||
void SetNetworkStateEstimate(webrtc::NetworkStateEstimate estimate);
|
||||
|
||||
// Resets the ProbeController to a state equivalent to as if it was just
|
||||
|
||||
Reference in New Issue
Block a user