Delayed tcp acknowledgement registry setting

  • Our IT department contacted me recently and asked if they should change the default TcpAckFrequency from 2 to 1 on SQL servers that I am managing - I manage the SQL part, they manage the server part. It is a MS setting that can be read about here:

    If I understand it correctly, it will cause the network to acknowledge each tcp segment and not only every second segment or when 200 ms elapses if no further segments are received.

    They (the IT department) found that another application observed (a felt) increased responsiveness when this setting was changed on that application's back end SQL server, but I think they did not actually measure it with facts, but they swear it has seen a highly noticeable performance increase in the web application.

    Does anyone here have any experience fiddling with that registry setting on SQL server machines?

  • I had never heard of this before, but reading the RFC, I don't see how changing this would improve performance outside of cases where applications that commence and complete processes in well under 200 ms, while performing single processes at a frequency of less than once every 200 ms

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply