What is typical TCP ACK response time in a good network? One would think it is in microseconds. We have a situation that is going over 200 milliseconds.
migration rejected from stackoverflow.com Oct 16 '13 at 12:43
This question came from our site for professional and enthusiast programmers. Votes, comments, and answers are locked due to the question being closed here, but it may be eligible for editing and reopening on the site where it originated.
closed as too broad by kce, Falcon Momot, Ward, Magellan, cole Oct 16 '13 at 12:43
There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs. If this question can be reworded to fit the rules in the help center, please edit the question.
"TCP delayed acknowledgment is a technique used by some implementations of the Transmission Control Protocol in an effort to improve network performance. In essence, several ACK responses may be combined together into a single response, reducing protocol overhead. However, in some circumstances, the technique can reduce application performance."
The Nagle algorithm can have some unusual edge cases that result in delays. If you want to confirm it is due to delayed ack, there is usually an operating system setting to disable the feature. It may be worth noting that on Windows, the delayed ACK timer is 200 ms.