Expands the fast-path lookup table in `HpackHuffmanDecoder` to 8 bits. Expands `kShortCodeTable` from 7 bits (124 entries) to 8 bits (254 entries), allowing all 5, 6, 7, and 8-bit HPACK Huffman codes (covering standard ASCII letters, digits, and common HTTP header punctuation) to be decoded in a single fast-path lookup step. This 508-byte lookup table is still compact enough to be CPU cache efficient. Based on benchmark runs against the current state, here is how this optimization compares: - **Overall Performance (`geomean`)**: **+5.44%** increase in throughput (from `95.22 MiB/s` to `100.4 MiB/s`). - **Largest Gains**: - `BM_DecodeChunkedInput/16`: **+13.58%** - `BM_DecodeLargeString/4k`: **+12.20%** - `BM_DecodeChunkedInput/64`: **+11.86%** - `BM_DecodeLargeString/1k`: **+11.63%** This optimization was generated by Gemini. The performance investigation that led to this improvement was motiviated by an article by the folks at Apoxy. * https://apoxy.dev/blog/oghttp2-vs-nghttp2 Protected by FLAGS_gfe2_reloadable_flag_hpack_huffman_decoder_optimizations. PiperOrigin-RevId: 962946960
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.
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.
Usage: quic_packet_printer server|client <hex dump of packet>
Usage: crypto_message_printer_bin <hex of message>
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>
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
Most log messages in QUICHE use the QUICHE_DLOG macro. In standalone quiche, these all either go to stderr, or are suppressed, based on the --stderrthreshold flag.
To send INFO level log messages to a file, you would therefore invoke
<binary> <args> > <logfile> 2>&1
Use the --helpfull flag for more.