3 ms·
>The results show that QUIC and HTTP/2 exhibit similar performance when the network bandwidth is relatively low (below ∼600 Mbps) >Next, we investigate more re
by M2Ys4U 2y ago
>The results show that QUIC and HTTP/2 exhibit similar performance when the network bandwidth is relatively low (below ∼600 Mbps)
>Next, we investigate more realistic scenarios by conducting the same file download experiments on major browsers: Chrome, Edge, Firefox, and Opera. We observe that the performance gap is even larger than that in the cURL and quic_client experiments: on Chrome, QUIC begins to fall behind when the bandwidth exceeds ∼500 Mbps.
Okay, well, this isn't going to be a problem over the general Internet, it's more of a problem in local networks.
For people that have high-speed connections, how often are you getting >500Mbps from a single source?
- sinuhe69 2y agoWell, I have other issues with QUIC: when I access Facebook with QUIC, the site often loads the first pages but then it kind of hung, force me to refresh the site, which is annoying. I didn’t know it’s a problem with QUIC, until I turned it off. Since then, FB & Co. load at the same speed, but don’t show this annoying behavior anymore!
- inetknght 2y ago> For people that have high-speed connections, how often are you getting >500Mbps from a single source? Often enough over HTTP/1.1 that discussions like this are relevant to my concerns.
- Mali- 2y agoAverage internet speed has increased by more than 10x in the last 10 years - we've got a few more multipliers in us.