←back to thread

QUIC is not quick enough over fast internet

(arxiv.org)
306 points carlos-menezes | 1 comments | 19 Oct 24 21:04 UTC | HN request time: 0s | source
Show context
jrpelkonen ◴[19 Oct 24 22:21 UTC] No.41891238[source]▶
Curl creator/maintainer Daniel Stenberg blogged about HTTP/3 in curl a few months ago: https://daniel.haxx.se/blog/2024/06/10/http-3-in-curl-mid-20...

One of the things he highlighted was the higher CPU utilization of HTTP/3, to the point where CPU can limit throughput.

I wonder how much of this is due to the immaturity of the implementations, and how much this is inherit due to way QUIC was designed?

replies(4): >>41891693 #>>41891790 #>>41891813 #>>41891887 #
cj ◴[19 Oct 24 23:39 UTC] No.41891693[source]▶
I’ve always been under the impression that QUIC was designed for connections that aren’t guaranteed to be stable or fast. Like mobile networks.

I never got the impression that it was intended to make all connections faster.

If viewed from that perspective, the tradeoffs make sense. Although I’m no expert and encourage someone with more knowledge to correct me.

replies(3): >>41891848 #>>41891912 #>>41893147 #
1. fulafel ◴[20 Oct 24 05:42 UTC] No.41893147[source]▶
That's how the internet works, there's no guaranteed delivery and TCP bandwidth estimation is based on when packets start to be dropped when you send too many.