Achieving Robust Mobile Web Content Delivery Performance Based on Multiple Coordinated QUIC Connections

Peng, Qian; Wang, Ning; Tafazolli, Rahim

doi:10.1109/access.2018.2804222

Cited by 21 publications

(10 citation statements)

References 36 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The combined score, ranging from 0 (lowest) to 100 (highest), ultimately serves as a comprehensive indicator of the user's performance and QoE for a given page. Not only is the percentile ranking system for each metric publicly available, so too is the weighted metric combining scheme 3 .…”

Section: Performance Metricsmentioning

confidence: 99%

“…QUIC is an emerging transport protocol which has been developed, and rolled out across services, by Google [1]. It is proposed as an alternative to the combination of TCP+TLS and provides features akin to TCP+TLS (such as loss and congestion control, security [2] and Forward Error Correction (FEC) [3]) as well as new ones like stream multiplexing.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

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

Saif

Lung

Matrawy

2021

ICC 2021 - IEEE International Conference on Communications

View full text Add to dashboard Cite

Google's QUIC (GQUIC) is an emerging transport protocol designed to reduce HTTP latency. Deployed across its platforms and positioned as an alternative to TCP+TLS, GQUIC is feature rich: offering reliable data transmission and secure communication. It addresses TCP+TLS's (i) Head of Line Blocking (HoLB), (ii) excessive round-trip times on connection establishment, and (iii) entrenchment. Efforts by the IETF are in progress to standardize the next generation of HTTP's (HTTP/3, or H3) delivery, with their own variant of QUIC. While performance benchmarks have been conducted between GQUIC and HTTP/2-over-TCP (H2), no such analysis to our knowledge has taken place between H2 and H3. In addition, past studies rely on Page Load Time as their main, if not only, metric. The purpose of this work is to benchmark the latest draft specification of H3 and dig further into a user's Quality of Experience (QoE) using Lighthouse: an open source (and metric diverse) auditing tool. Our findings show that, for one of H3's early implementations, H3 is consistently worse than H2 in terms of performance.

show abstract

Section: Performance Metricsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

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

Saif

Lung

Matrawy

2021

ICC 2021 - IEEE International Conference on Communications

View full text Add to dashboard Cite

show abstract

“…In [80], the authors evaluate the performance of multiple QUIC streams in LTE and WiFi networks. Their experiments show that for mobile web page, median and 95th percentile completion time can be improved by up to 59.1% and 72.3%, respectively, compared to HTTP.…”

Section: B Quicmentioning

confidence: 99%

Implementation and analysis of QUIC for MQTT

Kumar

Dezfouli

2019

Computer Networks

View full text Add to dashboard Cite

Transport and security protocols are essential to ensure reliable and secure communication between two parties. For IoT applications, these protocols must be lightweight, since IoT devices are usually resource constrained. Unfortunately, the existing transport and security protocols -namely TCP/TLS and UDP/DTLS -fall short in terms of connection overhead, latency, and connection migration when used in IoT applications. In this paper, after studying the root causes of these shortcomings, we show how utilizing QUIC in IoT scenarios results in a higher performance. Based on these observations, and given the popularity of MQTT as an IoT application layer protocol, we integrate MQTT with QUIC. By presenting the main APIs and functions developed, we explain how connection establishment and message exchange functionalities work. We evaluate the performance of MQTTw/QUIC versus MQTTw/TCP using wired, wireless, and long-distance testbeds. Our results show that MQTTw/QUIC reduces connection overhead in terms of the number of packets exchanged with the broker by up to 56%. In addition, by eliminating half-open connections, MQTTw/QUIC reduces processor and memory usage by up to 83% and 50%, respectively. Furthermore, by removing the head-of-line blocking problem, delivery latency is reduced by up to 55%. We also show that the throughput drops experienced by MQTTw/QUIC when a connection migration happens is considerably lower than that of MQTTw/TCP.

show abstract

“…Similarly, when testing iQUIC crossimplementation interoperability, developers often rely on direct chat conversations and live, concerted debugging in a Slack group [24] to diagnose problems, as it is difficult to interpret problem areas in other people's logs, which are often also lacking key information. While this method may work in these early days, as the number of developers, users and use cases [6,7,21] for iQUIC grows, a more scalable approach will be needed.…”

Section: Quic Researchmentioning

confidence: 99%

Towards QUIC debuggability

Marx

Lamotte

Reynders

et al. 2018

Proceedings of the Workshop on the Evolution, Performance, and Interoperability of QUIC

View full text Add to dashboard Cite

QUIC has been called the mother of all web protocols, as it deeply integrates aspects of TCP (reliability, flow control, congestion control, loss recovery), TLS (handshake, encryption keys) and HTTP/2 (streams, prioritization) together into one cross-layer implementation over UDP. However, such ambition comes at the cost of high complexity, which in turn leads to misinterpretations, bugs and unwanted behaviour in implementations. This was also witnessed in the recently standardized HTTP/2 protocol. We posit that QUIC should thus take a proactive approach in ensuring its testability and debuggability. To that end, this work introduces the first version of a common logging format for QUIC endpoints, called qlog. This format allows the capture of internal QUIC state that is not visible on the network. It is easily deployable and empowers the creation of reusable (visual) tools to aid in interpreting QUIC's behaviour. We implement and evaluate three such tools (a timeline, sequence diagram and congestion/flow control graph) in the proposed QUICvis toolset and show their usefulness in comparing behaviours across three competing QUIC implementations, as well as in performing root cause analysis on bugs and issues. We hope this work will foster the discussion on QUIC debuggability and that it will raise community awareness.

show abstract

Achieving Robust Mobile Web Content Delivery Performance Based on Multiple Coordinated QUIC Connections

Cited by 21 publications

References 36 publications

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

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

Implementation and analysis of QUIC for MQTT

Towards QUIC debuggability

Contact Info

Product

Resources

About