Flussonic Media Server documentation


To speed up the distribution of VOD, you can use the cache.

For original files from the cloud or HTTP server, cache is used.

For SSD drives, you must use a scheme with intermediate SSD caching. Cache segments using segment_cache.

File cache Anchor Anchor x2

You can ask Flussonic Media Server to save not chunks, but file content on disk, when source is a cloud or a remote HTTP server.

This mechanism can allow you to build a distributed CDN from several Flussonics because now even downloading will lead to caching whole file on edge.

And of course Flussonic Media Server will not download the same content twice, so simultaneous access to file is collapsed into single upstream request.

Here is configuration for file cache:

file vod {
  path http://big-central-origin.mycdn.tv/vod;
  cache /mount/ssd 400G;

Such configuration will download files on /mount/ssd on request: only required data will be fetched locally.

Segment cache for SSD Anchor Anchor x2

Today, one of the most popular ways to speed up serving content from a disk is using SSD storage.

Since solid state drives cost significantly higher than traditional HDs, quite often it makes sense to use the setup that involves intermediate SSD caching.

Flussonic Media Server can automatically cache the requested chunks for HLS and HDS on a disk, which allows to speed up delivery considerably. Make following configuration:

file vod {
    paths /mount/hdd1 /mount/hdd2 /mount/hdd3;
    segment_cache /mount/ssd1 20G 48h misses=2;

With this configuration, Flussonic Media Server maintains caching size limit of 20GB, deletes files older than 2 days and caches only the files requested more than twice.

Important! Mention please that before 4.6.14 this directive was named cache and you could specify reference to global cache directive. This has been changed and now you need to use current configuration.

Important! We do not recommend using segment_cache for traditional HDs!