You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When SRT is configured with SRTO_MAXBW=0 and SRTO_INPUTBW=0, SRT socket estimates the input bitrate in runtime.
However, this estimation is done by a socket individually. When a backup link is activated, the group supplies the backup socket with buffered and not yet acknowledged packets, submitted all one by one without any pacing. This would result in an overestimated input BW, and lead to an undesirably high BW limit.
Expected behavior
(Maybe) Estimate input BW when a packet is submitted to a group, and use the value for member sockets.
Versions Affected
SRT Version: all versions since experimental bonding was introduced (v1.4.2 and later), main/backup mode.
Credits
@J-Rogmann for conducting BW-related switching experiments.
The text was updated successfully, but these errors were encountered:
it looks like explicitly setting MAXBW doesn't help in case of switching from main to backup link. Please see following table:
I first ran into the issue when testing higher bandwidth streams with main/backup. Increasing rcvbuf helped. However, I also tried the same with a bandwidth limit of 10 Mbps on the 2 links and got pretty much the same results with MAXBWset or not set.
There could be done information interchange between the active link and the group, then forceful injecting this information into the newly activated socket so that it starts freshly with already prepared data over the other link.
Describe the bug
When SRT is configured with
SRTO_MAXBW=0
andSRTO_INPUTBW=0
, SRT socket estimates the input bitrate in runtime.However, this estimation is done by a socket individually. When a backup link is activated, the group supplies the backup socket with buffered and not yet acknowledged packets, submitted all one by one without any pacing. This would result in an overestimated input BW, and lead to an undesirably high BW limit.
Expected behavior
(Maybe) Estimate input BW when a packet is submitted to a group, and use the value for member sockets.
Versions Affected
SRT Version: all versions since experimental bonding was introduced (v1.4.2 and later), main/backup mode.
Credits
@J-Rogmann for conducting BW-related switching experiments.
The text was updated successfully, but these errors were encountered: