The first Media over QUIC CDN: Cloudflare

(moq.dev)

292 points kixelated | 1 comments | 22 Aug 25 18:24 UTC | HN request time: 0.206s | source

Show context

englishm ◴[22 Aug 25 19:11 UTC] No.44988596[source]▶

>>44987924 (OP) #

Hi! Cloudflare MoQ dev here, happy to answer questions!

Thanks for the award, kixelated. xD

replies(6): >>44989011 #>>44989230 #>>44989615 #>>44989828 #>>44990875 #>>45005783 #

tschellenbach ◴[22 Aug 25 19:49 UTC] No.44989011[source]▶

>>44988596 #

hi, I work on our webrtc streaming over at getstream.io

webrtc has a lot of annoying setup. but after it connects it offers low latency. how do you feel MoQ compares after the connection setup is completed? any advantages/ any issues?

replies(1): >>44989166 #

1. kixelated ◴[22 Aug 25 20:04 UTC] No.44989166[source]▶

>>44989011 #

QUIC/WebTransport gives you the ability to drop media, either via stream or datagrams, so you can get the same sort of response to congestion as WebRTC. However, one flaw with MoQ right now is that Google's GCC congestion controller prioritizes latency over throughput, while QUIC's TCP-based congestion controllers prioritize throughput over latency. We can improve that on the server side, but will need browser support on the client side.

As for the media pipeline, there's no latency on the transmission side and the receiver can choose the latency. You literally have to build your own jitter buffer and choose when to render individual frames.

↑