Google Git
Sign in
quiche / quiche / 1e07fb7ff9c4d2aa571951749e58dda573cbc5e7
commit1e07fb7ff9c4d2aa571951749e58dda573cbc5e7[log] [tgz]
authorQUICHE team <quiche-dev@google.com>Mon Oct 06 09:26:55 2025 -0700
committerCopybara-Service <copybara-worker@google.com>Mon Oct 06 09:27:34 2025 -0700
tree42ddefeb1e45ee89e0580d7e0f07ebd47693e2c6
parentaea0da8117de7f167e3d5da2127489a967b14645 [diff]
Inline unique_ptr field(s) to improve data locality.

This avoids unnecessary indirection and reduces last-level cache (LLC) misses.
Allocations made for the modified field(s) contribute billions of LLC misses.
In aggregate, these optimizations are expected to save up to
0.4% of fleet GCU (go/auto-unique-ptr-inline-orc).

This is an LLM-generated CL.
More information: go/auto-unique-ptr-inline-lsc

EDIT_CATEGORY: CATEGORY_INLINE_UNIQUE_PTR
FULLY_QUALIFIED_TYPE_NAME: http2::adapter::OgHttp2Session

#gwp-cl-impact
#inline-unique-ptr-fields

#mlpp-lsc-loop

#flyway_v2

From flyway_id: apostolakis/automated__migration/20250818023909/f4a680fa-a1c1-4cce-bc36-bb3a79b28b92

Tested:
    Local presubmit tests passed.

Protected by cannot be protected by flag since the type of a class field is changed.

PiperOrigin-RevId: 815759685
2 files changed
tree: 42ddefeb1e45ee89e0580d7e0f07ebd47693e2c6
  1. build/
  2. depstool/
  3. quiche/
  4. .bazelrc
  5. .bazelversion
  6. BUILD.bazel
  7. CONTRIBUTING.md
  8. LICENSE
  9. MODULE.bazel
  10. MODULE.bazel.lock
  11. README.md
  12. WHITESPACE
README.md

QUICHE

QUICHE stands for QUIC, Http, Etc. It is Google‘s production-ready implementation of QUIC, HTTP/2, HTTP/3, and related protocols and tools. It powers Google’s servers, Chromium, Envoy, and other projects. It is actively developed and maintained.

There are two public QUICHE repositories. Either one may be used by embedders, as they are automatically kept in sync:

To embed QUICHE in your project, platform APIs need to be implemented and build files need to be created. Note that it is on the QUICHE team's roadmap to include default implementation for all platform APIs and to open-source build files. In the meanwhile, take a look at open source embedders like Chromium and Envoy to get started:

To contribute to QUICHE, follow instructions at CONTRIBUTING.md.

QUICHE is only supported on little-endian platforms.

Build and run standalone QUICHE

QUICHE has binaries that can run on Linux platforms.

Follow the instructions to install Bazel.

sudo apt install libicu-dev clang lld
cd <directory that will be the root of your quiche implmentation>
git clone https://github.com/google/quiche.git
cd quiche
CC=clang bazel build -c opt //...
./bazel-bin/quiche/<target_name> <arguments>

There are several targets that can be built and then run. Full usage instructions are available using the --helpfull flag on any binary.

  • quic_packet_printer: from a provided packet, parses and prints out the contents that are accessible without decryption.

Usage: quic_packet_printer server|client <hex dump of packet>

  • crypto_message_printer: dumps the contents of a QUIC crypto handshake message in a human readable format.

Usage: crypto_message_printer_bin <hex of message>

  • quic_client: connects to a host using QUIC and HTTP/3, sends a request to the provided URL, and displays the response.

Usage: quic_client <URL>

  • quic_server: listens forever on --port (default 6121) until halted via ctrl-c.

  • masque_client: tunnels to a URL via an identified proxy (See RFC 9298).

Usage: masque_client [options] <proxy-url> <urls>

  • masque_server: a MASQUE tunnel proxy that defaults to port 9661.

Usage: masque_server

  • web_transport_test_server: a server that clients can connect to via WebTransport.

  • moqt_relay: a relay for the Media Over QUIC transport for publishers and subscribers can connect to.

Usage: moqt_relay