←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
skybrian ◴[19 Oct 24 22:03 UTC] No.41891114[source]▶
Looking at Figure 5, Chrome tops out at ~500 Mbps due to CPU usage. I don't think many people care about these speeds? Perhaps not using all available bandwidth for a few speedy clients is an okay compromise for most websites? This inadvertent throttling might improve others' experiences.

But then again, being CPU-throttled isn't great for battery life, so perhaps there's a better way.

replies(1): >>41893586 #
1. jeroenhd ◴[20 Oct 24 07:22 UTC] No.41893586[source]▶
These caps are a massive pain when downloading large games or OS upgrades for me as the end user. 500mbps is still fast but for a new protocol looking to replace older protocols, it's a big downside.

I don't really benefit much from http/3 or QUIC (I don't live in a remote area or host a cloud server) so I've already considered disabling either. A bandwidth cap this low makes a bigger impact than the tiny latency improvements.