Proceedings of the Internet Measurement Conference 2019
DOI: 10.1145/3355369.3355604
|View full text |Cite
|
Sign up to set email alerts
|

Modeling BBR's Interactions with Loss-Based Congestion Control

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

5
38
0

Year Published

2019
2019
2024
2024

Publication Types

Select...
3
3
2

Relationship

1
7

Authors

Journals

citations
Cited by 74 publications
(43 citation statements)
references
References 3 publications
5
38
0
Order By: Relevance
“…TCP Congestion Control. Many of the congestion control studies have especially looked at CUBIC [17] and BBR [10] and found that BBR dominates in under-buffered scenarios causing packet loss and making CUBIC back off, while it is disadvantaged in over-buffered scenarios [18,23,26,28]. Here, CUBIC, as a loss-based algorithm, fills the buffer and increases the queuing delay which makes BBR back off.…”
Section: Background and Related Workmentioning
confidence: 99%
“…TCP Congestion Control. Many of the congestion control studies have especially looked at CUBIC [17] and BBR [10] and found that BBR dominates in under-buffered scenarios causing packet loss and making CUBIC back off, while it is disadvantaged in over-buffered scenarios [18,23,26,28]. Here, CUBIC, as a loss-based algorithm, fills the buffer and increases the queuing delay which makes BBR back off.…”
Section: Background and Related Workmentioning
confidence: 99%
“…BBR is a delay/model-based CCA which converges on a fair share of bottleneck bandwidth by reducing its rate if the round-trip time increases, while periodically attempting to increase send rate to account for path/load changes. However, BBR traffic can consume 40 % of link capacity when multiplexed with loss-based CCAs, regardless of the number of competing flows [13]. When ensuring fair transit to all flows, this is hardly a desirable outcome; in fact, it's one which may frustrate clients or violate SLAs.…”
Section: I I T C P C O N G E S T I O N C O N T R O L C L a S S I F I C At I O Nmentioning
confidence: 99%
“…As a concrete use-case, we look at fine dynamics of TCP congestion control algorithms. Understanding and classifying them is important for network providers as inadequate choices have severe effects on transfer rates, especially in networks with high bandwidth-delay product [12] and in networks where multiple congestion control algorithms are used [13]. By using accurate congestion control diagnostics, operators will be able to infer sender problems (e.g., backlogged or applicationlimited senders), network inefficiencies (e.g., increased path latency and congestion), as well as receiver issues (e.g., delayed acknowledgements, small receiver windows) and fairness issues between delay-based and loss-based algorithms [13].…”
Section: Introductionmentioning
confidence: 99%
“…It is highly unlikely that many new services will set out to deliberately deploy algorithms that penalize the performance of their own flows -but given the difficulty of achieving perfect fairness ( §2.1.2) it is likely that this outcome may happen in some scenarios. 2 A very deployable, friendly algorithm would err on the side of harming their own connections where a more aggressive algorithm would err on the side of harming those 2 Consider Google's BBR, which, when one BBR flow competes with one Reno flow will only consume 40% of link capacity -less than its fair share [2,24]. Furthermore, 'background' CCA algorithms, such as TCP-Nice [23] and LEDBAT [20] deliberately only consume leftover bandwidth that is underutilized by other connections.…”
Section: 13mentioning
confidence: 99%