Add LS_VERBOSE logging for target bitrate in GoogCC
This will be used to investigate the effect of congestion window pushback on bandwidth esimation. There is currently no data available in event logs to analyze this in test runs. Bug: None Change-Id: I2397842e90fd4acab6306b03d1ee9daf62469ee3 Reviewed-on: https://webrtc-review.googlesource.com/c/121765 Reviewed-by: Konrad Hofbauer <hofbauer@webrtc.org> Reviewed-by: Sebastian Jansson <srte@webrtc.org> Commit-Queue: Evan Shrubsole <eshr@google.com> Cr-Commit-Position: refs/heads/master@{#26681}
This commit is contained in:
committed by
Commit Bot
parent
0179a3d224
commit
1d7bf89ad6
@ -625,6 +625,10 @@ void GoogCcNetworkController::MaybeTriggerOnNetworkChanged(
|
||||
update->probe_cluster_configs.insert(update->probe_cluster_configs.end(),
|
||||
probes.begin(), probes.end());
|
||||
update->pacer_config = GetPacingRates(at_time);
|
||||
|
||||
RTC_LOG(LS_VERBOSE) << "bwe " << at_time.ms() << " pushback_target_bps="
|
||||
<< last_pushback_target_rate_.bps()
|
||||
<< " estimate_bps=" << last_raw_target_rate_.bps();
|
||||
}
|
||||
}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user