commit 031ebc42e633d2b9b1e0b5dd2ee676800bf86807
author Erik Språng <sprang@webrtc.org> Mon Jan 16 11:41:48 2023
committer WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> Mon Apr 24 21:30:26 2023
tree 6630bef0cd4c6e9ae0f51fbecd65ebca0d0cdca6
parent 6a34c75d5d625cb0a1b51d5adce41be83ec6baa7

Increase RTP send buffer size from 64kb to 256kb.

Assuming 15Mbps video bitrate at 30fps, a single frame is 62500 bytes.
Add to that some fluctuations in encoder output rate and capture fps,
and frames can easily become larger than 64kb.
Given enough bandwidth and the bursty pacer, it will not be uncommon to
send the entire frame in one batch - and if the send buffer is at 64kb
then you will likely get packetloss already in the IPC packet socket,
even before the packet has reached the network card!

It's not entirely clear what the optimal size is, but given that the
receive buffer size was increased from 64kb to 256kb for high bandwidth
receive scenarios and had negligible negative effects I think it's
pretty safe to bump the send buffer to match.

There is a field trial available that can be used as circuit breaker
in case things turn south: WebRTC-SendBufferSizeBytes

Bug: webrtc:14780
Change-Id: I6c786d993181a882e6dce832ff56dc92d2a8a341
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/290985
Reviewed-by: Per Kjellander <perkj@webrtc.org>
Commit-Queue: Erik Språng <sprang@webrtc.org>
Cr-Commit-Position: refs/heads/main@{#39942}