ARC: Consistent, Low-Latency Delivery via Receiver-Side Scheduling
Michael Luby

TL;DR
ARC is a lightweight receiver-side protocol that restores sender-like timing in data delivery, reducing jitter and improving performance for latency-sensitive applications without requiring transport modifications.
Contribution
It introduces a novel receiver-only scheduling protocol, ARC, that maintains sender timing and order, enhancing application performance across various transport protocols.
Findings
ARC removes large jitter excursions in cloud gaming workloads.
ARC closely matches sender timing, improving perceptual smoothness.
Broader latency benefits are observed across TCP, QUIC, WebRTC, UDP, and RTP.
Abstract
Applications such as cloud gaming, video streaming, telemetry, ML inference, and data transfer provide a better experience when data is released at the receiver with timing reflecting how the data enters the sender. In practice, network delay variation and recovery dynamics at the receiver distort this timing even when transports deliver all packets correctly, producing visible jitter, stalls, and unstable playback. Many such applications operate best when delivery preserves this timing behavior and its implied order; out-of-order or irregular delivery can significantly degrade performance even when all data eventually arrives. We present a lightweight receiver-side release scheduling protocol, Adaptive Release Control (ARC), that restores this timing at the receiver. ARC releases recovered data in a manner that follows the sender's timing, maintaining ordering and limiting reordering…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
