Sharding and HTTP/2 Connection Reuse Revisited: Why Are There Still Redundant Connections?

10/27/2021
by   Constantin Sander, et al.
0

HTTP/2 and HTTP/3 avoid concurrent connections but instead multiplex requests over a single connection. Besides enabling new features, this reduces overhead and enables fair bandwidth sharing. Redundant connections should hence be a story of the past with HTTP/2. However, they still exist, potentially hindering innovation and performance. Thus, we measure their spread and analyze their causes in this paper. We find that 36 of the Alexa Top 100k websites cause Chromium-based webbrowsers to open superfluous connections. We mainly attribute these to domain sharding, despite HTTP/2 efforts to revert it, and DNS load balancing, but also the Fetch Standard.

READ FULL TEXT

page 1

page 2

page 3

page 4

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
05/03/2022

Exploring Proxying QUIC and HTTP/3 for Satellite Communication

Low-Earth Orbit satellites have gained momentum to provide Internet conn...
research
02/24/2021

Measuring HTTP/3: Adoption and Performance

The third version of the Hypertext Transfer Protocol (HTTP) is currently...
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
10/12/2018

Is the Web ready for HTTP/2 Server Push?

HTTP/2 supersedes HTTP/1.1 to tackle the performance challenges of the m...
research
10/18/2004

An Example of Clifford Algebras Calculations with GiNaC

This example of Clifford algebras calculations uses GiNaC (http://www.gi...
research
01/20/2010

Resolution scalability improvement for JPEG2000 standard color image

Removed by arXiv administration. This article was plagiarised from http:...

Please sign up or login with your details

Forgot password? Click here to reset