> As a guess, how many IceCast streams could be supported on one Linux PC > (say 1.5Ghz PC).Icast at one point had about 456 stations or so. We were able to do this (all the music was preencoded) with 8 machines quite reliably. Basically 4 machines sourced streams, and 4 machines served them. Only three machines were really needed, so failures were taken care of if only one machine failed. These were dual cpu p3-600s if I remember correctly. I'm not sure if only one set of four was dual or not. I suspect the source machines were duals and the icecast boxes were not. 8000 streams is quite a lot. Not to mention the amount of music you would need to make the content in 8000 streams more than trivial :) Or do you just mean 8000 simultaneous listeners? Because that is quite a different problem. jack. --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
Akos Maroy <darkeye@tyrell.hu> said:> Jack Moffitt wrote: > > Icast at one point had about 456 stations or so. We were able to do > > this (all the music was preencoded) with 8 machines quite reliably. > > Basically 4 machines sourced streams, and 4 machines served them. Only > > but the source machines: did they encode live audio, or send static > files to the server?Did you read the paragraph you quoted? "all the music was preencoded". Mike --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
Jack Moffitt wrote>8000 streams is quite a lot. Not to mention the amount of music you >would need to make the content in 8000 streams more than trivial :) > >Or do you just mean 8000 simultaneous listeners? Because that is quite >a different problem. >No 8000 streams, but that could take a few years to obtain. Probably around 2000 in the first year and they won't be just music either. Content will be provided by thousands the DJ's employed from all over the world to provide 2 hours a day of programming including announcements and advertisements. I've been employed to write software to help the DJ's compile their shows, and at our end, compile the playlists for each station and control the playout software. The first stations should start appearing in a couple of months. Michael Smith wrote: > The only major thing is this: do they require RTP (multicast)? Can you explain what this is and it's benefits? I tried googling it but didn't find anything useful. Thanks, Ross Levis. <p>--- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
Jack Moffitt wrote:> Icast at one point had about 456 stations or so. We were able to do > this (all the music was preencoded) with 8 machines quite reliably. > Basically 4 machines sourced streams, and 4 machines served them. Onlybut the source machines: did they encode live audio, or send static files to the server? --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
SOunds like whate we deployed at myplay.com - we had thousands of streams available but many of them would have zero listeners - so rather than sourcing that many I built a demand based streaming system that built the streams when they were delivered. S&M <p>----- Original Message ----- From: "Ross Levis" <ross@stationplaylist.com> To: <icecast@xiph.org> Sent: Wednesday, February 26, 2003 11:36 PM Subject: Re: [icecast] A large streaming project <p>> Jack Moffitt wrote> > >8000 streams is quite a lot. Not to mention the amount of music you > >would need to make the content in 8000 streams more than trivial :) > > > >Or do you just mean 8000 simultaneous listeners? Because that is quite > >a different problem. > > > No 8000 streams, but that could take a few years to obtain. Probably > around 2000 in the first year and they won't be just music either. > Content will be provided by thousands the DJ's employed from all over > the world to provide 2 hours a day of programming including > announcements and advertisements. > > I've been employed to write software to help the DJ's compile their > shows, and at our end, compile the playlists for each station and > control the playout software. The first stations should start appearing > in a couple of months. > > Michael Smith wrote: > > The only major thing is this: do they require RTP (multicast)? > > Can you explain what this is and it's benefits? I tried googling it but > didn't find anything useful. > > Thanks, > > Ross Levis. > > > --- >8 ---- > List archives: http://www.xiph.org/archives/ > icecast project homepage: http://www.icecast.org/ > To unsubscribe from this list, send a message to'icecast-request@xiph.org'> containing only the word 'unsubscribe' in the body. No subject is needed. > Unsubscribe messages sent to the list will be ignored/filtered.--- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
> Michael Smith wrote: > > The only major thing is this: do they require RTP (multicast)? > > Can you explain what this is and it's benefits? I tried googling it but > didn't find anything useful.<p>In brief: unicast (what icecast currently does) sends a copy of the stream to every listener. Thus, for a 32 kbps stream, your total bandwidth usage is approximately (there are a few little extras, but they end up being insignificant) number-of-listeners * 32 kbps. That adds up to a lot if you have thousands of listeners. With multicast, you basically send out only one copy of the stream (though you have overhead from each client reporting that it's connected, etc, so total bandwidth usage still scales upwards, just much slower), and the network infrastructure (routers, etc.) copies that to all the clients that are listening (description much simplified here, of course). The downside is that many ISPs don't have routers that are capable of multicast, and/or they don't have it enabled. So for really wide deployment you need both unicast and multicast available, ideally. Mike --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.