Slave Servers Requirements

This page describes our recomendations to add an slave server to giss network.

It's based on our experience and the actual requirements of the icecast master/slave infrastructure to allow all the mountpoints in use at one time.

Recomendations to add an icecast slave server to relay all mountpoints

This params works in the courrent situation where we have an stable 25/30 sources at the same time in giss, but that sometimes increase to about 40. This params are fine in the situation that 40 stables sources are online with 4 stables clients each one along all the month, what means 200 connections at the same time of about 100 kbps. Perhaps this is not a realistic situation at all but perhaps it's a good start point to measure this question.

Bandwidth: 20 mbps dedicated up/down

Monthly Transfer: 5TB / month

Server Software: as described in Servers Configuration

Server Hardware: 2,4 Ghz CPU / 512 RAM

And to add an icecast slave server to relay only some mountpoints

If you have X bandwidth and you want to join your server to giss, we recomend to tune icecast params like this:

X bandwith in kbps / 100 kbps (aprox for each connection) = max clients param in icecast conf
max clients param in icecast conf / 4 (clients by source) )= max sources param in icecast conf

If you have monthly transfer limits in your server you should know that one slave with about 25 sources online at the same time consumes each day about 30GB, so 1TB at month.

This way you can tune params in icecast like this:

X GB monthly transfer allowed / 40 = max sources param in icecast
max sources param in icecast * 4 (clients by source) = max clients param in icecast conf

Well, it's not a science as you can see. The 4 clients for source is an arbitrary number and the 100 kbps for each connection is more than is usually is. So take this notes only as an aproximation. ;)