Difference between revisions of "Slave Servers Requirements"

From Giss
(→‎Recomendations to add an icecast slave server to relay all mountpoints)
 
(One intermediate revision by the same user not shown)
Line 3: Line 3:
 
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.
 
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==
+
==Recomendations to add an icecast slave server to giss.tv==
  
−
Slave servers are now configured with relay-on-demand on. That means, that thay only get the stream from master when the master redirects a client to the slave. In this situation our recomendation is:
+
Slave servers are now configured with relay-on-demand on. That means, that they only get the stream from master when the master redirects a client to the slave. In this situation our recomendation is:
  
  
Line 17: Line 17:
  
 
'''Server Hardware''': 2,4 Ghz CPU / 512 RAM
 
'''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 simultaneus connections
 
−
1/5 max simultaneus connections = max sources param in icecast conf
 
−
4/5 max simultaneus connections = max clients 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 and without clients consumes each day about 20GB, or 600GB at month.
 
−
 
−
This way you can tune params in icecast like this:
 
−
 
−
X GB monthly transfer allowed / 25 (GB/connection/month) = max simultaneus connections
 
−
1/5 max simultaneus connections = max sources param in icecast conf
 
−
4/5 max simultaneus connections = 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 it usually is.
 
−
Besides, clients are not all the time connected, so this params refers to the ideal situation where the slave server is at 100%, in the proportion of 4 clients by source...
 
−
As this is not realistic at the moment, you could start with this recomendation and increase values step by step.
 
−
 
−
For instance, start with a conf of:
 
−
 
−
bandwidth 20 mbps
 
−
monthly transfer 1 TB
 
−
max sources 10 ( double of the recomended using the ''monthly transfer calculation'')
 
−
max clients 160 ( the recomended using the ''bandwidth calculation'')
 
−
 
−
is a good choice. ;)
 
−
 
−
As we can see, the bandwidth is more related to the max clients param, and the monthly tranfer allowed to the max sources params...
 

Latest revision as of 20:05, 3 August 2007

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 giss.tv

Slave servers are now configured with relay-on-demand on. That means, that they only get the stream from master when the master redirects a client to the slave. In this situation our recomendation is:


Bandwidth: 20 mbps dedicated up/down

Monthly Transfer: 1TB / month

Operative System: GNU/Linux 32 bits / 64 bits

Server Software: as described in Servers Configuration

Server Hardware: 2,4 Ghz CPU / 512 RAM

Retrieved from "http://giss.tv/wiki/index.php?title=Slave_Servers_Requirements&oldid=49"