search for: 16kpbs

Hi all, I have a question about the relationship between the "queue-size" and the "burst-size" <limits> parameters. Q: When a client connects is the burst-size immediately added to the queue-size? If this is the case then the slack for a 16kpbs client goes down from 50 sec (102400[queue-size] / 16kbps = 50 sec) to 18 seconds ( (102400 - 65536[burst-size]) / 16kpbs = 18 sec). I'm experiencing quite a few of the following lines in the DEBUG logging. It could be that the clients are really running too slowly, but chewing 32secs of the s...

On Wed, 2005-02-09 at 20:44, Klaas Jan Wierenga wrote: > Q: When a client connects is the burst-size immediately added to the > queue-size? no. > If this is the case then the slack for a 16kpbs client goes down from 50 sec > (102400[queue-size] / 16kbps = 50 sec) to 18 seconds ( (102400 - > 65536[burst-size]) / 16kpbs = 18 sec). > > I'm experiencing quite a few of the following lines in the DEBUG logging. It > could be that the clients are really running too slowly, bu...

Hi all, I'm running an Icecast-2.2 server with at peak times some 50 sources and 500 concurrent listeners all using low-bitrate 16kpbs streams. I'm experiencing some connection losses at these peak times ("Client connection died" message in error.log). The machine running Icecast has a 100Mbit connection to the internet. It is a Celeron 2.4Ghz machine with 1Gbyte of main memory. The CPU load at these peak times is n...

...cast-dev Onderwerp: Re: [Icecast-dev] icecast performance on many concurrentlow-bitrate streams On Wed, 2005-07-27 at 09:47, Klaas Jan Wierenga wrote: > Hi all, > > I'm running an Icecast-2.2 server with at peak times some 50 sources and 500 concurrent listeners all using low-bitrate 16kpbs streams. I'm experiencing some connection losses at these peak times ("Client connection died" message in error.log). > > The machine running Icecast has a 100Mbit connection to the internet. It is a Celeron 2.4Ghz machine with 1Gbyte of main memory. The CPU load at these peak t...