Static Files (HTTP/3)
The HTTP/3 Static Files profile serves 20 static files of various types over QUIC, simulating a browser loading page assets over HTTP/3.
Connections: 64, 512
How it works
- The load generator (oha) connects over HTTP/3 (QUIC) on port 8443
- Cycles through 20 URIs from
requests/static-h2-uris.txt(same file set as the HTTP/2 static test) - Each request fetches a different static file — CSS, JavaScript, HTML, fonts, SVGs, WebP images, and JSON
- The server returns pre-loaded file contents with the correct
Content-Type
What it measures
- HTTP/3 static asset serving — mixed content types and sizes over QUIC
- QUIC multiplexing — how well the framework handles varied concurrent requests
- Content-Type handling — correct MIME type mapping across file types
Static files
20 files (~360 KB total) pre-loaded into memory at startup:
| Type | Files | Examples |
|---|---|---|
| CSS | 5 | reset.css, layout.css, theme.css |
| JavaScript | 5 | app.js, vendor.js, router.js |
| HTML | 2 | header.html, footer.html |
| Fonts | 2 | regular.woff2, bold.woff2 |
| SVG | 2 | logo.svg, icon-sprite.svg |
| WebP | 3 | hero.webp, thumb1.webp, thumb2.webp |
| JSON | 1 | manifest.json |
Parameters
| Parameter | Value |
|---|---|
| Endpoint | 20 URIs under /static/* |
| Connections | 64, 512 |
| Parallelism | 128 per connection |
| Duration | 5s |
| Runs | 3 (best taken) |
| Load generator | oha |
| Port | 8443 (TLS + QUIC) |