Lowering game latency with WTFast tunneling
WTFast provides a small piece of software, approximately 2mb with a low memory footprint, to get you on your way without needing to know any Windows Registry tweaks or the need to purchase additional software like most tunneling service providers do. Once installed you simply type in the username and password, select the desired game and click play — it’s really that simple.

From this point the software will now take the .exe of the game and run its connection through the software and give it the best possible connection to the game server by choosing the route with the least amount of hops. WTFast will run in the background and continue to run even after the game has been closed until the software has been idle for more than 30 minutes, which at this point you will need to re-login to the software and relaunch the preferred game.
Probably the most impressive about WTFast’s software, aside from its tunneling ability, is the disable of the Nagle Algorithm feature within the registry for the user. In most cases, hard-core gamers will typically make this adjustment manually within the registry or by using software which can apply the changes.
TCP packets have a 40 byte header (20 bytes for TCP, 20 bytes for IPv4), which results in a 41 byte packet for 1 byte of useful information — thus in turn a huge overhead.
The Nagle Algorithm reacts horribly with TCP delayed acknowledgement. Applications that do two successive writes to a TCP connection experience a constant delay of up to 500 milliseconds which is also known as the “ACK delay”. For this reason, WTFast provides its application with the option to disable the Nagle Algorithm without having to modify the Windows registry manually. (Think of it as ‘trimming the fat’)
WTFast also provides users the option to select which WTFast server they prefer to connect to or simply allow the software to best choose the WTFast servers for them.
Comments























![Tomb Raider [NA] #Reborn Trailer](http://img.youtube.com/vi/yml1UGgXoEc/0.jpg)

