Difference between revisions of "Slave Servers Requirements"
From Giss
(→And to add an icecast slave server to relay only some mountpoints) |
|||
| 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 | + | ==Recomendations to add an icecast slave server to giss.tv== |
| − | Slave servers are now configured with relay-on-demand on. That means, that | + | 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: |
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
