# Making Chrome QUICer

DevFeed: [Making Chrome QUICer](<https://devfeed.tech/articles/making-chrome-quicer-4191.md>)

Original publisher: [Read original article](<https://blog.chromium.org/2024/12/making-chrome-quicer.html>)

Author: Chromium Blog (noreply@blogger.com)

Published: 2024-12-17T18:09:00Z

Content type: article

Language: en

Sources: [Chromium Blog](<https://devfeed.tech/sources/chromium-blog.md>)

Topics: [QUIC](<https://devfeed.tech/topics/quic.md>), [Web app](<https://devfeed.tech/topics/webapp.md>), [Google Chrome](<https://devfeed.tech/topics/google-chrome.md>), [TLS (Transport Layer Security)](<https://devfeed.tech/topics/tls.md>)

Tags: [chrome](<https://devfeed.tech/tags/chrome.md>), [connection-pooling](<https://devfeed.tech/tags/connection-pooling.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [cryptography](<https://devfeed.tech/tags/cryptography.md>), [dns](<https://devfeed.tech/tags/dns.md>), [google](<https://devfeed.tech/tags/google.md>), [google-search](<https://devfeed.tech/tags/google-search.md>), [handshake](<https://devfeed.tech/tags/handshake.md>), [http](<https://devfeed.tech/tags/http.md>), [http-2](<https://devfeed.tech/tags/http-2.md>), [http-3](<https://devfeed.tech/tags/http-3.md>), [ietf](<https://devfeed.tech/tags/ietf.md>), [ip](<https://devfeed.tech/tags/ip.md>), [latency](<https://devfeed.tech/tags/latency.md>), [lookup](<https://devfeed.tech/tags/lookup.md>), [memory](<https://devfeed.tech/tags/memory.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [none](<https://devfeed.tech/tags/none.md>), [october](<https://devfeed.tech/tags/october.md>), [optimizing](<https://devfeed.tech/tags/optimizing.md>), [packets](<https://devfeed.tech/tags/packets.md>)

## AI overview

Chrome enabled HTTP/3's ORIGIN frame and Server's Preferred Address by default in M131 to improve connection reuse and reduce round-trip time. ORIGIN lets a server specify which domains may share a connection, avoiding extra DNS checks and new connections when IP addresses mismatch; Chrome metrics suggest nearly 20% of HTTP/3 connections would otherwise be unnecessary because of such mismatches. New connections can add DNS, handshake, cryptographic, CPU and memory costs, and 0-RTT may fail or be unavailable for non-safe requests. Server's Preferred Address lets the server, after handshake confirmation, suggest a different IP for the client to migrate to, potentially bypassing a load balancer or a longer Anycast route. Chrome tests reported migration success above 99% and average RTT reductions of 40-80%. The excerpt says Google's Media CDN was the only service widely advertising an alternative address so far.

## Source excerpt

In October 2020, Chrome enabled HTTP/3 by default. HTTP/3 (RFC 9114) runs over IETF QUIC (RFC9000). Default-enabling HTTP/3 in Chrome resulted in improved performance compared not only HTTP/1 and HTTP/2, but also Google QUIC. Benefits included reduced Google search latency and fewer rebuffers for YouTube. The journey to optimizing performance did not end when HTTP/3 was default enabled. Recent advancements include the implementation of the HTTP/3 ORIGIN frame (RFC 9412) and Server's Preferred Address (RFC 9000 Section 9.6). The former enhances connection coalescing, while the latter reduces a connection's round trip time (RTT). Both features have been enabled by default in M131, which was released to Stable on 11/19. ORIGIN Frame When a connection is established for a specific hostname, the server's certificate typically contains numerous other hostnames for which the server is authoritative. However, a client cannot immediately send requests for those other hostnames on that connection without first performing a DNS lookup for the other hostname and verifying that the IP address of the connection matches the resolved address. This additional DNS resolution introduces latency and significantly reduces the likelihood of connection pooling due to potential IP mismatches. The metrics from Chrome indicate that nearly 20% of HTTP/3 connections would be unnecessary if not for this IP mismatch. Creating a new connection, even with QUIC 0-RTT, is expensive in terms of latency, memory, and CPU usage. This is because: DNS resolution adds latency unless cached locally in Chrome's DNS cache. Both client and server must send multiple packets to complete a QUIC handshake. TLS necessitates CPU-intensive asymmetric cryptography on both ends. The congestion controller begins in its default state, potentially leading to under or over-sending. 0-RTT might fail. Non-safe requests aren't sent via 0-RTT. More connections consume more memory. Additionally, features like HTTP priorities (R