Norman Maurer wrote:
> Hi Pierre,
>
> after setting the option it seems to sent the whole time. But it
seems to "overload" the device. I still notice problems with stuck
sound. Is there any way I could throttle the outgoing traffic so it
whould not overload the device ?
>
> bye
> Norman
>
Hi,
you can search here :
http://www.nabble.com/forum/Search.jtp?query=throttle&local=y&forum=16869&daterange=0&startdate=&enddate=
http://en.wikipedia.org/wiki/Nagle_algorithm
"Congestion Control in IP/TCP Internetworks (RFC896) describes what he
called the 'small packet problem', where an application repeatedly emits
data in small chunks, frequently only 1 byte in size. Since TCP packets
have a 40 byte header (20 bytes for TCP, 20 bytes for IPv4), this
results in a 41 byte packet for 1 byte of useful information, a huge
overhead. This situation occurs in Telnet sessions, where keypresses
generate a single byte of data which is transmitted immediately. Worse,
over slow links, many such packets can be in transit at the same time,
potentially leading to congestion collapse.
The Nagle algorithm works by coalescing a number of small outgoing
messages, and sending them all at once. Specifically, as long as there
is a sent packet for which the sender has received no acknowledgment,
the sender should keep buffering its output until it has a full packet's
worth of output, so that output can be sent all at once."
You had better look for the optimum writeBufferSize
(StreamWriteFilter.setWriteBufferSize(int writeBufferSize)) when Nagle
algorithm is disabled.
- small size => overload
- big size (when Nagle algorithm is enabled the size is ~1500) =>
problem of latency)
Another solution : you keep Nagle algorithm enabled but you decrease the MTU
Pierre-Louis
