Minimal latency and unreliable streams #1186

okbaswc · 2021-01-25T04:55:01Z

okbaswc
Jan 25, 2021

How is it possible with MSQUIC to drop the reliability/order/acknowledgements of a stream, and get as close to raw UDP as possible in latency?

Answered by nibanks

Per-spec streams are reliable, ordered streams of data. You cannot just "drop" that feature, but there are two possible solutions to your problem:

You use Datagrams (DatagramSend) instead of streams. This allows you to send and receive chunks (not streams) of data over the QUIC connection. There is less overhead than streams.
We could add support for delivering stream data immediately to the app as we receive it, not buffering it or trying to reorder out of order data, but then the app would have to handle all that. I'm not sure this would help all that much though.

nibanks · 2021-01-29T15:54:53Z

Per-spec streams are reliable, ordered streams of data. You cannot just "drop" that feature, but there are two possible solutions to your problem:

You use Datagrams (DatagramSend) instead of streams. This allows you to send and receive chunks (not streams) of data over the QUIC connection. There is less overhead than streams.
We could add support for delivering stream data immediately to the app as we receive it, not buffering it or trying to reorder out of order data, but then the app would have to handle all that. I'm not sure this would help all that much though.

0 replies