A Performance Perspective on Web Optimized Protocol Stacks: TCP+TLS+HTTP/2 vs. QUIC
arXiv:1906.07415 · doi:10.1145/3340301.3341123
Abstract
Existing performance comparisons of QUIC and TCP compared an optimized QUIC to an unoptimized TCP stack. By neglecting available TCP improvements inherently included in QUIC, comparisons do not shed light on the performance of current web stacks. In this paper, we can show that tuning TCP parameters is not negligible and directly yields significant improvements. Nevertheless, QUIC still outperforms even our tuned variant of TCP. This performance advantage is mostly caused by QUIC's reduced RTT design during connection establishment, and, in case of lossy networks due to its ability to circumvent head-of-line blocking.
Cited by in corpus (11)
- Measuring HTTP/3: Adoption and Performance
- An Early Benchmark of Quality of Experience Between HTTP/2 and HTTP/3 using Lighthouse
- QUIC is not Quick Enough over Fast Internet
- QUIC on the Highway: Evaluating Performance on High-rate Links
- Perceiving QUIC: Do Users Notice or Even Care?
- On the Interplay between TLS Certificates and QUIC Performance
- QUIC Hunter: Finding QUIC Deployments and Identifying Server Libraries Across the Internet
- Evaluating the Benefits: Quantifying the Effects of TCP Options, QUIC, and CDNs on Throughput
- ReACKed QUICer: Measuring the Performance of Instant Acknowledgments in QUIC Handshakes
- QUIC Steps: Evaluating Pacing Strategies in QUIC Implementations
- Waiting for QUIC: Passive Measurements to Understand QUIC Deployments