View previous topic :: View next topic |
Author |
Message |
adepa
Joined: 17 Jul 2008 Posts: 5
|
Posted: Thu Jul 17, 2008 12:50 am Post subject: Slow Listeners |
|
|
I'm getting hundreds of slow listeners.
Is that a problem?
Anyone know why and how to solve it?
Are the slow listeners connected and listening? |
|
Back to top |
|
|
karlH Code Warrior
Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Thu Jul 17, 2008 2:22 am Post subject: |
|
|
The slow listeners count accumulates over time. It's a measure of listeners that get kicked off the stream for being too slow. You can work out the maximum lag icecast will allow by dividing queue-size by the bitrate and don't forget that a burst-size is part of the queue.
You may be using a low tolerance for the queue length and the bitrate or the network links may be max'd out causing listeners to starve.
karl. |
|
Back to top |
|
|
adepa
Joined: 17 Jul 2008 Posts: 5
|
Posted: Thu Jul 17, 2008 10:44 am Post subject: Slow Listeners |
|
|
Thank you very much. Can you please explain to me how to do this? I have 3 different streams running. Listeners have a choice of 96k, 36k or 20k
Thanks |
|
Back to top |
|
|
adepa
Joined: 17 Jul 2008 Posts: 5
|
Posted: Thu Jul 17, 2008 12:26 pm Post subject: burst-size, queue-size, bit rate |
|
|
Please see below. any suggestions for improvemnt?
We have 3 streams, bit rates set at 96, 40 and 32
<icecast>
<limits>
<sources>5</sources>
<clients>500</clients>
<threadpool>5</threadpool>
<queue-size>102400</queue-size>
<client-timeout>30</client-timeout>
<header-timeout>15</header-timeout>
<source-timeout>10</source-timeout>
<burst-on-connect>5</burst-on-connect>
<client-timeout>90</client-timeout>
<header-timeout>80</header-timeout>
<source-timeout>90</source-timeout>
<burst-size>97536</burst-size>
</limits> |
|
Back to top |
|
|
karlH Code Warrior
Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Thu Jul 17, 2008 12:58 pm Post subject: |
|
|
Based on those then you have configured an extremely low tolerance. queue-size is 100k (very small) with a burst of around 97k of that when the listener connects. you have around 3kbytes tolerance before they get kicked off. The default queue-size for some time now has been 512k which at 96kbits (12kbytes/s) is about 42 secs. So increase your queue-size.
karl. |
|
Back to top |
|
|
adepa
Joined: 17 Jul 2008 Posts: 5
|
Posted: Thu Jul 17, 2008 1:12 pm Post subject: Slow Listeners |
|
|
Thank you soo much. Are you saying I can just increase the queue size to 512K and that should help?
Is the burst 97k ok or should i reduce that to 64 as well?
How about <burst-on-connect>5</burst-on-connect> ?
What does that mean?
Thank you for all your help. U really Rock! |
|
Back to top |
|
|
karlH Code Warrior
Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Thu Jul 17, 2008 1:18 pm Post subject: |
|
|
increasing the queue-size from 100k is something you really should do even if the burst is 64k, the figure of 97k for burst is not a significant concern, the default of 64k is only set like that because it is a common setting for prebuffering in players.
burst on connect is ignored but in older versions it was used to either set burst-size to 64k or 0
karl. |
|
Back to top |
|
|
adepa
Joined: 17 Jul 2008 Posts: 5
|
Posted: Thu Jul 17, 2008 5:19 pm Post subject: Slow Listeners |
|
|
Thank you Karl. I made the change. Increased the queue to 512. I just saw listeners log on and drop off to slow. Am I doing something else wrong? |
|
Back to top |
|
|
karlH Code Warrior
Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Thu Jul 17, 2008 9:21 pm Post subject: |
|
|
If there isn't some weird problem in the stream (eg incorrect samplerate) then it will be down to max'd out network links or maybe network errors. Whether that is at your end or on the route to the listener is something we cannot say.
karl. |
|
Back to top |
|
|
|