BaishanCloud/EdgeNext Achieves 12-Second Global Median Cache Purge Time
CDN Planet measured the cache purge speed for BaishanCloud/EdgeNext, reporting a global median purge time of 12 seconds across the US, UK, and Hong Kong based on 528 measurements. This data indicates how quickly content updates or removals propagate across the CDN infrastructure for streaming operators. The purge time is defined as the interval between sending a purge request to the CDN API and actually getting a cache MISS.
Key Takeaways
- BaishanCloud/EdgeNext recorded a global median cache purge time of 12 seconds across 528 measurements.
- Purge times were measured from US, UK, and Hong Kong locations, with the US showing the quickest median at 10 seconds.
- The 90th percentile for global purge speed was 19 seconds, while the 99th percentile was 38 seconds.
- CDN Planet defines purge time as the period from CDN API request to content being marked as a cache MISS.
Why It Matters
For streaming operators, fast cache purge speeds directly translate to quicker content updates or removals on their CDN, critical for correcting errors, localized content changes, or complying with takedown notices. A 12-second median purge time indicates efficient content propagation. This metric influences user experience and operational agility, as delayed purges can lead to end-users accessing outdated content. Industry experts will continue to compare these benchmarks across various CDNs, with players like Azure CDN, Cloudflare, and CloudFront also tracked by CDN Planet for similar performance data. Watch for comparative performance trends as CDNs innovate to reduce these critical delivery times.
Read full article at cdnplanet.com