Medusa Panel › Settings › CDN
Medusa has a built-in CDN that serves your stream output from every server in the cluster, not just the one running the stream. You add servers once, then turn the CDN on and viewers can be served from whichever node is closest or least busy.
Add your servers first
A CDN needs more than one server. Add each node under Medusa Panel › Server › Manage Servers before you enable the CDN — see Adding nodes.
Enable the CDN
Open Medusa Panel › Settings › CDN:
- CDN —
Enabledmakes the HLS/DASH output of every stream reachable on all servers. - Live Stream tmpfs Cache —
Enabledprefers RAM (tmpfs) for live CDN objects; new objects fall back to disk automatically when memory runs low. Movies and series (VOD) always stay on persistent storage. - HLS/DASH Live Prefetch —
Enabledmakes the nodes subscribe to new HLS/DASH files as the origin publishes them (push).Disabledmakes a node pull only the manifests and segments a player actually requests. HTTP-TS is never prefetched. - CDN Load Balancing — spread new viewers across healthy nodes; see Load balancing and metrics.
The tmpfs cache cuts disk wear for live traffic; prefetch lowers the time-to-first-segment on a node, at the cost of it pulling everything the origin publishes whether or not a viewer is on that node yet.
The CDN serves the packaged output (HLS/DASH). How that output is produced is set per stream and in the packaging options — see Packaging and caching.
Related
- Adding nodes — register the servers the CDN uses.
- Load balancing and metrics — how new sessions are spread.
- Packaging and caching — the output the CDN distributes.
- Master and slave nodes — how the cluster is organised.