Cloudflare Origin Range Requests cut R2 time to first byte by 50%
Cloudflare has launched Origin Range Requests, a new feature that automates byte-range request management for large files using its Pingora-based caching architecture. The update eliminates manual range-size configuration, aiming to reduce latency and inter-data-center traffic for streaming and large-object delivery workloads.
Key Takeaways
- Internal testing on R2 storage showed a 50% reduction in p99 time to first byte for both cache hits and misses.
- Tiered cache traffic for large-object workloads dropped by 6% after implementing the new coordinator logic.
- The update replaces the old nginx-based cache-slicing method with fixed-size chunks stored via Pingora.
- New coordinator logic allows a single request to combine cached data, in-flight downloads, and origin fetches.
Why It Matters
This update addresses a critical inefficiency in CDN architecture where seeking within large video files often triggered massive, unnecessary data transfers from the origin. By moving away from manual range-size configuration to a chunk-based coordinator, streaming platforms can reduce egress costs and improve playback start times for seek-heavy content like 4K video. Within the broader ecosystem, this shift toward automated cache management reduces the technical debt for engineers who previously had to balance memory pressure against origin load. Watch for Cloudflare to make this the default behavior for specific media file types to further reduce global network waste.
Companies in this story
In short
Cloudflare has launched Origin Range Requests, a new feature that automates byte-range management for large files using Pingora-based architecture. By replacing manual cache-slicing with a chunk-based coordinator, the update reduces time to first byte by 50% and lowers inter-data-center traffic, significantly improving playback performance and efficiency for high-bandwidth streaming platforms.
FAQ
What is Cloudflare Origin Range Requests?
It is a new feature that automates byte-range management for large files, replacing manual cache-slicing methods with a more efficient, chunk-based coordinator logic built on Pingora.
How much did time to first byte improve with this update?
Internal testing on R2 storage demonstrated a 50% reduction in p99 time to first byte for both cache hits and misses.
Why is this update important for streaming platforms?
It reduces egress costs and improves playback start times for seek-heavy content like 4K video by eliminating unnecessary data transfers from the origin.
How does the new coordinator logic work?
The new logic allows a single request to combine cached data, in-flight downloads, and origin fetches, streamlining how large files are delivered.
Read full article at blog.cloudflare.com
Hear Mark's take on this story
Mark Donnigan covers this story in today's StreamingMeme Podcast episode.
Enjoy our coverage?
Add StreamingMeme as a preferred source on Google to see more of our streaming news at the top of your Search results.
Add as preferred source
