Page 1 of 1

Lower Your Ping?

Posted: Wed Jan 02, 2008 10:45 pm
by Hybuir
A guildie of mine posted this and I was a bit skeptical, and it has to deal with modifying and making variables in regedit... so I gave it a whirl and it dropped my ping 100 ms! woo. Even have the screenshots to prove it.

http://juniordimas.com/wow/before.jpg
http://juniordimas.com/wow/after.jpg
*Don't know how my hearth got up to over a thousand hours
TT wrote:pasted from http://www.arenajunkies.com/showthread.php?t=6330
_________________________________________________________________________________

Dropped my latency from 210-230 to 75-90 MS.

As well as increased my framerate, all by simply disabling Nagles Algorhtm which will be disabled next patch, if you cannot wait like myself then use this copied from mmo-champion.com, I personally experience no negative side effectsf rom doing this unless you count an FPS increase and a 150ms reduction a negative side effect =P.

"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\Servic es\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\Paramet ers

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).

This will be fixed in 2.3.2, but if you don't wanna wait another 1-3 weeks you can do the above steps.

If you want to verify the commands you can do so on this microsoft link:

http://technet2.microsoft.com/window....mspx?mfr=true

If you don't have the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\ directory, you can download and apply this file to your registry.

http://rapidshare.com/files/77255080/msmq.reg.html

No negative side effects are known from applying this patch, my upload/download speeds remained exactly the same, there is a different fix for windows Vista users though doing this may still work for you.

Posted: Thu Jan 03, 2008 9:13 am
by Rollie
Tinkering with your registry can be risky business. Be warned!

Given that, I'm going to try it =)

Posted: Thu Jan 03, 2008 9:21 am
by Hybuir
lol, thought you would. I hate restarting tho... stupid AVG antivirus always has me restart every 3 days *shakes fist* it did take me about a week before I did this :-P

Posted: Mon Jan 21, 2008 4:50 am
by Phreeze
didnt change anything :-/

Posted: Mon Jan 21, 2008 9:14 am
by DM.
Worked for me :)

Posted: Mon Jan 21, 2008 10:25 am
by Hybuir
They implemented the diabling of the algorithm in patch 2.3.2

Posted: Mon Jan 21, 2008 11:59 am
by DM.
The Nagle algorithm is the 2nd part with disabling the TCPNoDelay. Blizzard didn't implement the first part with the TcpAckFrequency

Posted: Mon Jan 21, 2008 4:45 pm
by Hybuir
so doing this + patching = uber low ping... well lower than just patching?

Posted: Mon Jan 21, 2008 8:40 pm
by DM.
yar