[Veserv]

I am baffled you can even get to six figure LoC implementing QUIC. Having done the majority of a QUIC implementation before deciding I needed to design a new protocol that fixes QUIC's performance limitations, a minimal, but fully functional and performant implementation with zero dependencys (except for cryptography) should only take maybe 5,000 lines.

If you use the default parameters with such a implementation you will likely cap out at a pretty slow ~10 Gbps/core, but if you reduce the ACK frequency you can probably get to ~30-50 Gbps/core without too much trouble.

[dpark]

Doesn’t QUIC already have an extension for negotiating ACK frequency?

[Veserv]

They do, it is a draft [1]. There are other design flaws that also limit data path performance (ignoring encryption) to probably something on the order of just 30-50 Gbps/core though I would not be too surprised if you could get ~100 Gbps/core in a well-behaved case.

[1] https://datatracker.ietf.org/doc/draft-ietf-quic-ack-frequen...