A Performance Perspective on Web Optimized Protocol Stacks: TCP+TLS+HTTP/2 vs. QUIC

06/18/2019
by   Konrad Wolsing, et al.
0

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.

READ FULL TEXT

page 1

page 2

page 3

page 4

research
10/17/2019

Perceiving QUIC: Do Users Notice or Even Care?

QUIC, as the foundation for HTTP/3, is becoming an Internet reality. A p...
research
07/18/2017

Domain-Sharding for Faster HTTP/2 in Lossy Cellular Networks

HTTP/2 (h2) is a new standard for Web communications that already delive...
research
04/04/2020

An Early Benchmark of Quality of Experience Between HTTP/2 and HTTP/3 using Lighthouse

Google's QUIC (GQUIC) is an emerging transport protocol designed to redu...
research
06/20/2023

On Cross-Layer Interactions of QUIC, Encrypted DNS and HTTP/3: Design, Evaluation and Dataset

Every Web session involves a DNS resolution. While, in the last decade, ...
research
04/12/2021

Exploring the Attack Surface of WebSocket

Over the years, with the advancement of technology, Web technology has m...
research
08/13/2019

ConfigTron: Tackling network diversity with heterogeneous configurations

The web serving protocol stack is constantly changing and evolving to ta...
research
11/19/2016

Tracking Words in Chinese Poetry of Tang and Song Dynasties with the China Biographical Database

Large-scale comparisons between the poetry of Tang and Song dynasties sh...

Please sign up or login with your details

Forgot password? Click here to reset