Held-Connection Benchmarks (CON-1M, CON-1M-TLS, CON-5M): Validation Checks
The profiles drive GET /baseline11?a=1&b=2, the baseline endpoint unchanged, so an entry subscribed to connections-5m, connections-1m-tls or connections-1m is run through the full baseline validation suite: the arithmetic, the Content-Type, the randomized-input anti-cheat, the TCP fragmentation checks, and the exhaustive per-byte fragmentation sweep.
A listener on every address
One check is specific to these profiles. CON-5M spreads its five million connections over 127.0.0.1 to 127.0.0.160, CON-1M its million over 127.0.0.1 to 127.0.0.32, because one client address can hold only about 64.5K connections to one server address and port. A server bound to 127.0.0.1 or localhost passes every baseline check and refuses all but one of those addresses, so validation sends the baseline request to both ends of the range:
| check | request | expected |
|---|---|---|
| GET /baseline11 on 127.0.0.2 | GET http://127.0.0.2:8080/baseline11?a=13&b=42 | 55 |
| GET /baseline11 on 127.0.0.160 | GET http://127.0.0.160:8080/baseline11?a=13&b=42 | 55 |
To pass, listen on 0.0.0.0 or [::] (an IPv6 wildcard listener accepts IPv4 connections too, unless it sets IPV6_V6ONLY). The benchmark repeats the probe before it launches anything, and a server that fails it gets an empty row with the reason rather than millions of connect errors.
Over TLS
CON-1M-TLS (connections-1m-tls) spreads its million over 127.0.0.1 to 127.0.0.32 on the h1 TLS port, so both ends of that range are asked there, over TLS 1.3: the load generator offers no other version, and a server without it would fail every handshake of the run.
| check | request | expected |
|---|---|---|
| GET /baseline11 over TLS 1.3 on 127.0.0.2 | GET https://127.0.0.2:8081/baseline11?a=13&b=42 (TLS 1.3, HTTP/1.1) | 55 |
| GET /baseline11 over TLS 1.3 on 127.0.0.32 | GET https://127.0.0.32:8081/baseline11?a=13&b=42 (TLS 1.3, HTTP/1.1) | 55 |
What the run checks
- Held, not just offered. gcannon counts the connections still open at the end of the window; on CON-1M (
connections-1m) the harness counts the server's established sockets on :8080 from the kernel's socket table after it. Either way a server that dropped connections, or never accepted them, shows its real count in the Held column. rate_ratio. Achieved over offered in the window, published with the row. A connection that never opened sends nothing, so a fleet only partly held falls short here as well as in Held, and the score falls proportionally.- CPU from outside. As on the other fixed-rate profiles, CPU is read by the harness from the container's cgroup rather than reported from inside it, over the window only.