A — Ours over AGVC (Spark 2)In-country grey DNS → Spark 1 gateway → Spark 2
Waiting for ladder...
Same content. Three delivery paths. Measured live.
Device GPU hardware-decodes AV1/HEVC/H.264 at the edge. Bytes encoded and originated on Spark 2 (Colombo). Panel A uses the in-country AGVC path; Panel B crosses overseas IP transit (US-3 Chicago).
Source honesty: Blender open movie “Tears of Steel” 4K studio master (6.7 GB, royalty-free).
The 8K rung is upscaled to 7680×4320 (lanczos) during SVT-AV1 encode on Spark 2 — genuine 8K delivery + device decode, not natively rendered at 8K.
B — Ours over overseas transit (US-3)Same ladder, Chicago origin — no domestic cache advantage
Waiting for ladder...
C — Google / YouTube baselineLazy-loaded privacy-enhanced embed — throughput not measurable cross-origin
Equivalent clip: Tears of Steel (Blender Foundation)
Runs on Google infrastructure; sets its own cookies. Panels A/B are fully sovereign on Sri Lankan soil.
YouTube metrics: first-frame, quality, rebuffer count (IFrame API only).
Cache engine — cold vs warm (Panel A origin)nginx proxy_cache + 1 MB slice — watch X-Cache-Status flip MISS → HIT
Cold vs warm delta appears here after each run.
Sovereignty: Encode + origin both on Spark 2 in Sri Lanka. Domestic AGVC delivery = lower latency, sustained 4K/8K, no international IP transit for the media leg.
Viewer device GPU decodes — no quality loss from our encode method (SVT-AV1 CPU, one-time offline step).
Caveat: This proves sovereign in-country delivery for SL viewers — not a claim to beat a global CDN for international audiences.
Caveat: This proves sovereign in-country delivery for SL viewers — not a claim to beat a global CDN for international audiences.