Paper detail

A study of HTTP/2's Server Push Performance Potential

Modern web pages have complex structures comprised of up to hundreds of different resources, such as scripts and images. Server push is an HTTP/2 feature enabling servers to preemptively send resources to clients before they realize they need them to render a page. The objective is to reduce the amount of time the browser has to wait for data to be transferred, and consequently total page load time. Our goal in this work is to quantify how much server push can actually reduce web page load times. We approach the problem from both theoretical and experimental perspectives. We start by deriving an upper bound for the load time reduction afforded by server push. Then we proceed to actually evaluate an idealized push implementation on the Alexa Top 100 global sites, against a non-push HTTP/2 baseline. Our results show a linear relationship between latency and the benefit of server push. Moreover, pages with taller dependency trees tend to benefit the most from it.

preprint2022arXivOpen access
0citations
0reviews
0saves
Nocode
Nodataset
0institutions

Next steps

Decide what to do with this paper

Use like or dislike for the fast social read. The more specific scholarly feedback stays available below when needed.

Log in to curate

Reading frame

Keep the important context close to the paper

Keep the important signals around this paper in one place: votes, save state, collection context, reviews and the metadata you need before deciding what to do next.

Institutions

Add specific reaction

Move through the context

Research map

Open full explorer

Move through nearby people, institutions, topics and adjacent work without leaving the paper page.

Building this graph slice

BZPEER is loading the nearby papers, people, topics and institutions for this page.

Structured reviews

0 review(s)

ContributeLeave structured feedbackUse the review template when you have a concrete strength, concern or method question.Open review form

No structured reviews yet. High-signal critique starts here.

Work discussion

0 comment(s)

DiscussAdd a high-signal commentKeep quick notes, caveats and replication pointers separate from formal reviews.Open comment form

No discussion yet. The first strong comment sets the tone.