Hi again Ben,
Actually, 802 bytes is not a big message in this problem :) It's rather
small.
I did a rather extensive test in this subject... sadly I am not a TCP
implementation expert, so I cannot give a good explanation. But my results
were more or less like this:
-big messages (more than 8KB-1
Hi David,
Thank you for the advice. I didn't think the tcpNoDelay would have an
effect since I was looking at relatively large messages :)
Simply changing the connection URL solved the immediate problem, send
latency dropped right down into the microseconds as expected. So far I
haven't ha
Hi there bwatrous,
Your average sent time for the problematic RUN 1 (40ms) indicates that your
problem is most probably caused by the bad Nagle's algorithm / Delayed ACK
timeout interaction. This timeout is 40ms in Linux and 200ms in Windows /
other systems.
In short, the solution is to enable T
