Elitist Jerks - View Single Post

Cenuij · 12/10/07, 7:55 PM

Originally Posted by Binkenstein

Also, using the following regkey should help (I'm usually 500+ on a good day, was just short of 300 after using it).

From the second page of the thread Baalz listed above New registry entry for controlling the TCP Acknowledgment (ACK) behavior in Windows XP and in Windows Server 2003

I found the TcpAckFrequency=1 registry change beneficial too (for WoW). I went from 450-600ms to 250-320ms. It was much less effort than adding a loopback redirect and netcat hack on my firewall, and a little less effort than using FreeCap to Internode's proxy.

As other mentioned, enabling TCP_NODELAY on the socket connection that the client uses is a trivial change for Blizzard's developers to add to their client code. It's ~3 lines of C on a UNIX application using setsockopt(3), and the Windows equivalent should be about the same.

Thanks again to Yarre for the hints on the delayed ACK problem and solution. Thanks also to Internode for working on a (separate) solution.