Difference between revisions of "Slave Servers Requirements"

From Giss
(New page: This page describe our recomendations to add a slave server to giss network. It's based on our experience and the actual requirements of the icecast master/slave infrastructure to allow '...)
 
 
(15 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
This page describe our recomendations to add a slave server to giss network.
+
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.
 
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==
  
−
==Recomendations to add an icecast slave server to relay all mountpoints==
+
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''': minimum 20 mbps dedicated up/down
 
  
−
'''Monthly Transfer''': 2TB / month
+
'''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 Software''': as described in [[Servers Configuration]]
  
 
'''Server Hardware''': 2,4 Ghz CPU / 512 RAM
 
'''Server Hardware''': 2,4 Ghz CPU / 512 RAM
−
 
−
 
−
==Recomendations 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 paramm in icecast conf / 4 (clients by source) )= max source 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 source param in icecast
 
−
max source 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. ;)
 

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"