Self-tested on loopback on the build worker:
- TCP: multi-stream throughput OK (72 Gb/s loopback, 2 threads).
- UDP: sendmmsg/recvmmsg path OK — 1.25 Mpps @64b, 4 threads; server tracks received pps + loss via sequence gaps.
- JSON output OK. CPU pin (
--cpus) + NUMA (--numa) accepted.
- Anti-OOM guard OK: refuses absurd alloc (100000 threads × 9000 B → 54931 MiB > 25%-RAM limit).
Loopback numbers are functional checks, not benchmarks (kernel-loopback bound). Real numbers = real NIC (see other issue).
Self-tested on loopback on the build worker:
--cpus) + NUMA (--numa) accepted.Loopback numbers are functional checks, not benchmarks (kernel-loopback bound). Real numbers = real NIC (see other issue).