Icecast - Mar 2005 - how can I identify disconnect due to low

Hello Karl

In your reply in this case you mentinoned:
>>
>> Check your TCP buffers sizes as well, a larger RTT (ping) will require
a
>> larger TCP window to maintain the same maximum bitrate.
>>
>> karl.
We had troubles with the problem of "disconnecting when client has fallen 
too far behind" and we solved it temporarily by increasing the queue-size 
and the number of threads, but it is just a workaround solution and it works 
because our listeners only listen during about 1- 1,5 hour.

Do you have some extra information around the impact of the size of the 
TCP-window in relation to this problem ? Our clients mostly have a dial-in 
connection. We are streaming with 16kbps or 24kbps

Thank you in advance for any information

With kind regards,
Henk vd Ridder

On Mon, 2005-03-07 at 19:15, Henk van de Ridder wrote:
> Do you have some extra information around the impact of the size of the 
> TCP-window in relation to this problem ? Our clients mostly have a dial-in 
> connection. We are streaming with 16kbps or 24kbps
The TCP window is just the amount of un-acknowledged data in the
connection, so if the window size is too small then the connection is
throttled and the bitrate drops. That sort of thing would lead to a
client fallen too far behind. So it depends on the expected bitrate and
the round trip time (RTT, ping).

The simplest way is to make sure the server enables TCP window scaling
and check the listener OS for their TCP settings. Make sure they have
either TCP window scaling enabled or at least a large enough receive
window

karl.