This little regedit fix can decrease your latency by 100-150 ms (depending on what you currently have). Still works in 2.3.2 even though it shouldn't.
Edit: I recommend you make a backup of the registry keys that are getting edited. The change could adversely effect your d/l speeds, surf speeds etc. All that you need to do then is to run the backup files and reboot."1 - TcpAckFrequency - NOTE if you are running Windows Vista this setting may not have any effect - a hotfix is needed which i'm tracking down. This works fine under Windows XP
Type "regedit" in windows "run.." dialog to bring up registry menu
Then find:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\
There will be multiple NIC interfaces listed in there, find the one you use to connect to the internet, there will be several interfaces listed (they have long names like {7DBA6DCA-FFE8-4002-A28F-4D2B57AE8383}. Click each one, the right one will have lots of settings in it and you will see your machines IP address listed there somewhere. Right-click in the right hand pane and add a new DWORD value, name it TcpAckFrequency, then right click the entry and click Modify and assign a value of 1.
You can change it back to 2 (default) at a later stage if it affects your other TCP application performance. it tells windows how many TCP packets to wait before sending ACK. if the value is 1, windows will send ACK every time it receives a TCP package.
2 - TCPNoDelay
This one is pretty simple (Discussed here)
Type "regedit" in windows "run.." dialog to bring up registry menu
Then find:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Parameters
Right-click in the right hand pane and add a new DWORD value, name it TCPNoDelay, then right click the entry and click Modify and assign a value of 1.
Click Ok and close the registry editor, then reboot your PC."
Basically, this fix is deactivating the Nagle algorithm to improve your ping. If you don't want to do it you can just wait for the 2.3.2 patch as it's supposed to deactivate it too, but I don't think you can test it on PTRs right now because the updated patch notes from the latest PTR Build (7705) are actually for the upcoming build (7710).