Knowledge Base
Test Profiles
H/3
Baseline (HTTP/3)
Implementation Guidelines

Implementation Guidelines

$ Production
# Tuned
* Engine
Must use the framework native QUIC/HTTP3 support with default configuration.
May tune QUIC parameters, congestion control, and UDP buffer sizes.
No specific rules. Ranked separately from frameworks.

The HTTP/3 Baseline profile tests raw throughput over QUIC, the UDP-based transport protocol that powers HTTP/3.

Connections: 64, 512

How it works

  1. The load generator (oha) connects to the server over HTTP/3 (QUIC) on port 8443
  2. Sends GET /baseline2?a=1&b=1 requests with 128 parallel requests per connection
  3. The server parses query parameters and returns the sum

What it measures

  • QUIC transport performance - UDP-based connection handling
  • HTTP/3 framing overhead - compared to HTTP/1.1 and HTTP/2
  • TLS 1.3 integration - QUIC mandates encryption
  • Framework QUIC implementation quality - varies significantly across frameworks

Expected request/response 

GET /baseline2?a=1&b=1 HTTP/3
HTTP/3 200 OK
Content-Type: text/plain

2

Parameters

ParameterValue
EndpointGET /baseline2?a=1&b=1
Connections64, 512
Parallelism128 per connection
Duration5s
Runs3 (best taken)
Load generatoroha
Port8443 (TLS + QUIC)

Notes

  • HTTP/3 support is not universal - only frameworks with native QUIC support participate
  • Results may show higher variance than HTTP/1.1 and HTTP/2 due to oha limitations
  • See the oha load generator docs for known issues
Validation