AI & ML
BBR's Sharing Behavior with CUBIC and Reno
arXiv cs.NI0 views
arXiv:2505.07741v2 Announce Type: replace Abstract: TCP BBR's behavior has been explained by various theoretical models, and in particular those that describe how it co-exists with other types of flows. However, as new versions of the BBR protocol have emerged, it remains unclear to what extent the high-level behaviors described by these models apply to the newer versions. In this paper, we systematically evaluate the most influential steady-state and fluid models describing BBR's coexistence with loss-based flows over shared bottleneck links. Our experiments, conducted on a new experimental platform (FABRIC), extend previous evaluations to additional network scenarios, enabling comparisons between the two models and include the recently introduced BBRv3. Our findings confirm that the steady-state model accurately captures BBRv1 behavior, especially against single loss-based flows. The fluid model successfully captures several key behaviors of BBRv1 and BBRv2 but shows limitations, in scenarios involving deep buffers, large numbers of flows, or intra-flow fairness. Importantly, we observe clear discrepancies between existing model predictions and BBRv3 behavior, suggesting the need for an updated or entirely new modeling approach for this latest version. We hope these results validate and strengthen the research community's confidence in these models and identify scenarios where they do not apply.
Source:https://arxiv.org/abs/2505.07741PreviousTowards Energy- and QoS-aware Load Balancing for 5G Advanced: Leveraging O-RAN to Achieve Sustainability and Energy EfficiencyNextInvariant Discovery for Networked Systems
Related posts
We tested memory retrieval on DolphinBench. Plain keyword search exposed our own regression.
0dev.to
Global stocks tumble as AI panic grips markets after Democrats' midterm success
0Hacker News
Turning GPT GIFs into a cat film: what smoothing fixed, and what it didn’t
0dev.to AI
I Stopped Writing a New API Client for Every AI Model
0dev.to AI
The smallest feature we shipped started a war (the friendly kind)
0dev.to AI
Authorized is not proven: what the FDA's AI device list does and doesn't tell you
0dev.to AI