6 ms·
Horses for courses. Is anyone suggesting QUIC for gigantic bulk transfers? TCP isn’t great for latency-sensitive small transfers so we will have QUIC. QUIC will
by jeffbee 6y ago
Horses for courses. Is anyone suggesting QUIC for gigantic bulk transfers? TCP isn’t great for latency-sensitive small transfers so we will have QUIC. QUIC will not be perfect for everything, like TCP is not perfect for everything.
- drewg123 6y agoI'm pretty sure YouTube uses QUIC for video streaming today, which is a similar workload to ours.
- jeffbee 6y agoI think that indicates more about the economics of YouTube than anything. Probably their frontend CPU costs would have to go up by a factor of ten thousand before it even began to approach their costs for compression and storage of user uploads.
- virattara 6y ago> I'm pretty sure YouTube uses QUIC for video streaming today Is there any media transfer protocol based on QUIC?
- drewg123 6y agoI found an article from 4 years ago saying that 20% of youtube's traffic was QUIC: https://www.fiercewireless.com/wireless/youtube-driving-more-quic-based-traffic-mobile-vasona https://www.fiercewireless.com/wireless/youtube-driving-more...
- detaro 6y agoYoutube is delivering video over HTTP. HTTP3, i.e. it is transported over QUIC.
- elithrar 6y agoLucas Pardue, who is the IETF QUIC WG chair, has a great talk from Mux's Demuxed conf last year on using QUIC as a transport for UDP streaming: https://www.youtube.com/watch?v=Zdkjd7-EWmQ&feature=emb_title https://www.youtube.com/watch?v=Zdkjd7-EWmQ&feature=emb_titl... This is not dissimilar from SRT.
- elithrar 6y agoYep: YouTube currently delivers over gQUIC and h3 (IETF QUIC). We advertise the following alt-svc for most devices: > h3-29=":443"; ma=2592000,h3-T051=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43" HTTP/3 (over IETF QUIC) is still not as widely deployed due to lesser client support, but that's growing as both Chrome[1], Firefox and Apple (in iOS Safari, when enabled) adopt it and the latest drafts. [1]: https://blog.chromium.org/2020/10/chrome-is-deploying-http3-and-ietf-quic.html https://blog.chromium.org/2020/10/chrome-is-deploying-http3-...
- masklinn 6y ago> Horses for courses. Is anyone suggesting QUIC for gigantic bulk transfers? Anyone who's looking to replace HTTP/1.1 and HTTP/2 with HTTP/3? AFAIK QUIC is completely integral to that, in order to avoid this issue you'll need a mixed deployment of HTTP/3 and an older version of the standard.
- anderspitman 6y agoI just hope we don't remove support for HTTP/1.1 from our stacks entirely. 2/3 are great for performance but an order of magnitude more complex.
- M2Ys4U 6y agoI imagine that HTTP/2 use will almost entirely move to HTTP/3, and HTTP/1.1 usage will decline but there'll still be plenty of it around.
- cpeterso 6y agoCloudflare’s Radar dashboard has recent measurements of HTTP/1, 2, and 3 traffic (near the bottom of the page): https://radar.cloudflare.com/ https://radar.cloudflare.com/ Right now, HTTP/1.x is 23% of traffic, HTTP/2 is 75%, and HTTP/3 is just 2%. Since this is about overall traffic (visible to Cloudflare), big sites like Google and Facebook dominate. All that HTTP/3 traffic is probably Chrome users watching YouTube.
- jeffbee 6y agoI’m positive that an organization the size of Netflix which has dedicated itself absolutely to pushing 200gbps out of every individual box can figure out how to run HTTP 1.1 forever.
- otabdeveloper4 6y ago"Whee, the magic number went up, better upgrade". Despite Google meddling with the standards, "HTTP/3" isn't HTTP.