16 HTTP requests are sent back-to-back on each connection before waiting for responses. Uses a lightweight GET /pipeline endpoint that returns a fixed response, isolating raw I/O and pipeline handling from application logic. Frameworks that batch pipelined requests from the read buffer gain a significant advantage. Container pinned to 64 CPU threads (cores 0-31, 64-95). Learn more →

Each connection is closed and re-established after 10 requests, forcing repeated TCP handshakes. Same mixed GET/POST workload as baseline. Measures how efficiently a framework handles connection setup and teardown — important for real-world scenarios where clients don't maintain long-lived connections. Container pinned to 64 CPU threads (cores 0-31, 64-95). Learn more →