←back to thread

QUIC is not quick enough over fast internet

(arxiv.org)
306 points carlos-menezes | 2 comments | 19 Oct 24 21:04 UTC | HN request time: 0.406s | source
1. p1necone ◴[19 Oct 24 22:14 UTC] No.41891200[source]▶
I thought QUIC was optimized for latency - loading lots of little things at once on webpages and video games (which send lots of tiny little packets - low overall throughput but highly latency senstive) and such. I'm not surprised that it falls short when overall throughput is the only thing being measured.

I wonder if this can be optimized at the protocol level by detecting usage patterns that look like large file transfers or very high bandwidth video streaming and swapping over to something less cpu intensive.

Or is this just a case of less hardware/OS level optimization of QUIC vs TCP because it's new?

replies(1): >>41891429 #
2. zamalek ◴[19 Oct 24 22:57 UTC] No.41891429[source]▶
It seems that syscalls might be the culprit (ACKs occur completely inside the kernel for TCP, where anything UDP acks from userspace). I wonder if BGP could be extended for protocol development.