Statistics and usage
The SDK reports delivery signals asynchronously. Reporting failure must not interrupt playback.
| Metric | Meaning |
|---|---|
| P2P download | Bytes delivered from peers and counted toward quota |
| CDN fallback | Bytes delivered from your CDN when P2P is unavailable |
| Peer availability | Eligible peers and regions observed by the session |
| Fallback reason | Why a segment or session returned to CDN |
| P2P upload | Bytes shared by the current device with other viewers |
CDN offload calculation and validation
CDN offload is calculated from delivered bytes:
CDN offload = P2P download / (P2P download + CDN fallback) × 100%
MeshStream does not promise a fixed offload percentage. Use the measured result for your workload. Results depend on same-content concurrency, viewer progress, network reachability between viewers, geographic distribution, media format, segment duration, and cache policy.
To validate a workload, use the same application and playback URL across multiple real devices and record P2P download and CDN fallback bytes separately. Measure live and on-demand playback independently. Do not combine warm-up, abnormal exits, or single-viewer periods with the stable-concurrency window. Record the time range, device count, platform, region, media protocol, and segment duration so each run can be reproduced and compared.
Use application, key, platform, region, event, and reason as investigation dimensions. Keep session IDs and time ranges when opening a support case.
Workload and measurement guides
- P2P CDN for live streaming: evaluate concurrency, reachability, latency, and CDN fallback before expanding a rollout.
- Video CDN cost and offload guide: distinguish delivered bytes from net cost and compare representative workloads.