使用 Lighthouse 对 HTTP/2 和 HTTP/3 之间体验质量的早期基准测试
An Early Benchmark of Quality of Experience Between HTTP/2 and HTTP/3 using Lighthouse
AI总结：
本文旨在填补H2与H3基准测试的空白，利用Lighthouse工具深入探究H3最新草案规范的用户体验质量，发现H3早期实现多数指标表现较差但平均吞吐量更高。
摘要：
Google的QUIC（GQUIC）是一种新兴传输协议，旨在减少HTTP延迟。它部署于各大平台并作为TCP+TLS的替代方案，功能丰富：提供可靠的数据传输和安全通信。它解决了TCP+TLS的（i）队头阻塞（HoLB），（ii）连接建立时过多的往返时间，以及（iii）根深蒂固的问题。IETF正致力于标准化下一代HTTP（HTTP/3，或H3）的交付，并采用其自己的QUIC变体。尽管已在GQUIC和HTTP/2-over-TCP（H2）之间进行了性能基准测试，但据我们所知，H2和H3之间尚未进行此类分析。此外，过去的研究依赖页面加载时间作为其主要（甚至是唯一）指标。本工作旨在对H3的最新草案规范进行基准测试，并使用Lighthouse（一款开源且指标丰富的审计工具）进一步深入探究用户的体验质量（QoE）。我们的研究结果表明，对于H3的早期实现之一，H3在大多数情况下表现较差，但实现了更高的平均吞吐量。
英文摘要：
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 mostly worse but achieves a higher average throughput
机构、总结、中文摘要均由AI分析而来，可能存在错误，请以论文正文为准。
