2018
DOI: 10.1007/978-3-319-93527-0_5
|View full text |Cite
|
Sign up to set email alerts
|

Web Performance Characteristics of HTTP/2 and Comparison to HTTP/1.1

Abstract: Abstract. The HTTP/1.1 protocol has long been a staple on the web, for both pages and apps. However, it has started to show its age, especially with regard to page load performance and the overhead it entails due to its use of multiple underlying connections. Its successor, the newly standardized HTTP/2, aims to improve the protocol's performance and reduce its overhead by (1) multiplexing multiple resources over a single TCP connection, (2) by using advanced prioritization strategies and by introducing new fe… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1

Citation Types

0
3
0

Year Published

2020
2020
2024
2024

Publication Types

Select...
1
1
1

Relationship

0
3

Authors

Journals

citations
Cited by 3 publications
(3 citation statements)
references
References 18 publications
(34 reference statements)
0
3
0
Order By: Relevance
“…We speculate Figure 10. The per-segment bitrate and RTT of the client a 1 in subscenario 2-B that this was because of the deliveries of the wasted PUSH_PROMISE frames that caused the server to delay the downloads of the responses for those segments [39]. Since the client performed similar to the HTTP/1.1 during this period, such large RTTs were unavoidable and resulted in bandwidth underutilization [6,7].…”
Section: Discussionmentioning
confidence: 99%
“…We speculate Figure 10. The per-segment bitrate and RTT of the client a 1 in subscenario 2-B that this was because of the deliveries of the wasted PUSH_PROMISE frames that caused the server to delay the downloads of the responses for those segments [39]. Since the client performed similar to the HTTP/1.1 during this period, such large RTTs were unavoidable and resulted in bandwidth underutilization [6,7].…”
Section: Discussionmentioning
confidence: 99%
“…In contrast, for the case of the Proactive method (Figures 9b and 10b), the RTT drastically increased for a consecutive number of segments (nine segments for subscenario 2-A and 12 segments for subscenario 2-B) after the new clients joined at the 100th segment. We speculate that this was because of the deliveries of the wasted PUSH_PROMISE frames that caused the server to delay the downloads of the responses for those segments [39]. Since the client performed similar to the HTTP/1.1 during this period, such large RTTs were unavoidable and resulted in bandwidth underutilization [6,7].…”
Section: Discussionmentioning
confidence: 99%
“…As a result, the client discards S n i+1 and sends request for S n i+1 , which completely compromises the mechanism of the server push. Hence, not only does the client fail to make use of the advantages discussed in Section 2, but also it wastes the server's network resources utilized for the push segment [39].…”
Section: Handling the Server Push Mechanismmentioning
confidence: 99%