←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: 0s | source
Show context
austin-cheney ◴[19 Oct 24 22:26 UTC] No.41891263[source]▶
EDITED.

I preference WebSockets over anything analogous to HTTP.

Commented edited because I mentioned performance conditions. Software developers tend to make unfounded assumptions/rebuttals of performance conditions they have not tested.

replies(6): >>41891324 #>>41891333 #>>41891426 #>>41891517 #>>41891549 #>>41891575 #
1. quotemstr ◴[19 Oct 24 22:36 UTC] No.41891324[source]▶
> * String headers > * round trips > * many sockets, there is additional overhead to socket creation, especially over TLS > * UDP. Yes, in theory UDP is faster than TCP but only when you completely abandon integrity.

Have you ever read up on the technical details of QUIC? Every single of one of your bullets reflects a misunderstanding of QUIC's design.

replies(1): >>41891440 #
2. Aurornis ◴[19 Oct 24 22:58 UTC] No.41891440[source]▶
Honestly the entire comment is a head scratcher, from comparing QUIC to HTTP (different layers of the stack) or suggesting that string headers are a performance bottleneck.

Websockets are useful in some cases where you need to upgrade an HTTP connection to something more. Some people learn about websockets and then try to apply them to everything, everywhere. This seems to be one of those cases.