Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What does tcpOutAckDelayed mean, and what causes it to count up? is it an indication of problems or not?

The sun doco isnt clear!

Thanks, Dan

share|improve this question

Delayed ACK is basically the tcp stack being smart. Pasted:

Delayed ACK means TCP doesn't immediately ack every single received TCP segment. (When reading the following, think about an interactive ssh session, not bulk transfer.) If you receive a single lone TCP segment, you wait 100-200ms, on the assumption that the receiving application will probably generate a response of some kind. (E.g., every time sshd receives a keystroke, it typically generates a character echo in response.) You don't want the TCP stack to send an empty ACK followed by a TCP data packet 1ms later, every time, so you delay a little, so you can combine the ACK and data packet into one. So far so good. But what if the application doesn't generate any response data? Well, in that case, what difference can a little delay make? If there's no response data, then the client can't be waiting for anything, can it? Well, the application-layer client can't be waiting for anything, but the TCP stack at the end can be waiting: This is where Nagle's Algorithm enters the story:

Read more at TCP Performance problems caused by interaction between Nagle's Algorithm and Delayed ACK

share|improve this answer
Another example of where TCP delayed ack was part of a problem that impacted performance is at <a href="">http://…; – mas Jul 31 '09 at 12:19

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.