Add ability to control TaskQueuePacedSender holdback window.
Holdback window can be specified as absolute time and in terms of packet send times. Example: WebRTC-TaskQueuePacer/Enabled,holdback_window:20ms,holdback_packet:3/ If current conditions have us running with 2000kbps pacing rate and 1250byte (10kbit) packets, each packet send time is 5ms. The holdback window would then be min(20ms, 3*5ms) = 15ms. The default is like before 1ms and packets no take into account when TQ pacer is used, parameters have no effect with legacy process thread pacer. Bug: webrtc:10809 Change-Id: I800de05107e2d4df461eabaaf1ca04fb4c5de51e Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/233421 Commit-Queue: Erik Språng <sprang@webrtc.org> Reviewed-by: Philip Eliasson <philipel@webrtc.org> Reviewed-by: Henrik Boström <hbos@webrtc.org> Cr-Commit-Position: refs/heads/main@{#35266}
This commit is contained in:
committed by
WebRTC LUCI CQ
parent
7bb853f549
commit
0f86c1f125
@ -103,6 +103,7 @@ class PacingController {
|
||||
|
||||
// Sets the pacing rates. Must be called once before packets can be sent.
|
||||
void SetPacingRates(DataRate pacing_rate, DataRate padding_rate);
|
||||
DataRate pacing_rate() const { return pacing_bitrate_; }
|
||||
|
||||
// Currently audio traffic is not accounted by pacer and passed through.
|
||||
// With the introduction of audio BWE audio traffic will be accounted for
|
||||
|
||||
Reference in New Issue
Block a user