Scaling and server sizing
One creekX server carries an installation's media: live streams, cameras and 24/7 channels. Size it to the load. The web app and API can run as several copies on a shared database.
How far one server goes
| Load | Typical capacity | Limited by |
|---|---|---|
| Incoming 1080p streams, recorded | ~0.017 core each | CPU, disk |
| WebRTC viewers, 1080p at 2.5 Mbit/s | ~350 per Gbit/s of network | Network |
| LL-HLS viewers | ~890 Mbit/s per 1 Gbit/s port | Network |
| IP cameras, 1080p at 3 Mbit/s | ~250 per 8-core server | Network, storage |
| Several qualities (ABR) | ~0.6 core per live | CPU |
Full results: Load testing results. Exact sizing: the pricing calculator.
Growing past one server today
- More viewers: put HLS behind a CDN; playlists and segments cache like any web files.
- More streams or cameras: run more than one installation, each with its own licence, split by site or event.
-
Web app and API: run several copies behind a load balancer (roles
apiandlibrary), with onemediarole per installation.
Clustering
Origin and edge servers for viewers, then several media servers that share streams and cameras and take over from each other, are in development. Talk to us about a deployment that needs them.