分片和HTTP/2连接重用再探:为什么还有冗余连接?
Sharding and HTTP/2 Connection Reuse Revisited: Why Are There Still Redundant Connections?
摘要:
HTTP/2和HTTP/3避免了并发连接,而是在单个连接上多路复用请求。除了启用新功能外,这还减少了开销并实现了公平的带宽共享。因此,冗余连接应该成为HTTP/2的历史。然而,它们仍然存在,可能会阻碍创新和绩效。因此,本文对它们的传播进行了测量,并分析了它们的原因。我们发现,36% - 72%的624万HTTP存档和78%的Alexa Top 100 k网站会导致基于Chromium的Web浏览器打开多余的连接。我们主要将这些归因于域分片,尽管HTTP/2努力恢复它,以及DNS负载均衡,但也是Fetch标准。
英文摘要:
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% - 72% of the 6.24M HTTP Archive and 78% 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.
机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。