This video improved my latency considerably

[Giblet1]

There's a whole heap of **** you can do.

Not really, I usually get about 200-220ms at night when all the Americans are asleep, seems blizzards servers can't handle it during the day.

[Marius]

Well that's probably why. In that last post I said there's not much improvement beyond that and in the first post identified this as more relevant to 300+ latency.

[Giblet1]

, I still wanted to see if it would do anything during the day/peek times. Bouncing around between 300-400 sucks

[lucassot]

:( , I still wanted to see if it would do anything during the day/peek times. Bouncing around between 300-400 sucks

Yeah same. It's decent when they are asleep heh.

[GoToadGo]

:( , I still wanted to see if it would do anything during the day/peek times. Bouncing around between 300-400 sucks

Yeah same. It's decent when they are asleep heh.

Even when they're asleep it isn't good enough. 180ms+ will get you killed a lot in the higher difficulties(hell act 2+) if you hit a rough champion pack. The amount of times I've been blown up or mortared due to THINKING I was safe is getting ridiculous and is making me want to stop playing altogether. I'm not even going to bother with Inferno as I know I'll just rage at it all the time. This game is really highlighting the fact that they need to establish an oceanic set of servers if they're going to continue with their online only mindset. 200ms is fine for WoW as the game play doesn't need that split second timing(well PVE doesn't anyway, I can't speak for PVP as I never did that while I played) but at times this game really needs that split second timing we just can't get when we have such high latency.

[lucassot]

:( , I still wanted to see if it would do anything during the day/peek times. Bouncing around between 300-400 sucks

Yeah same. It's decent when they are asleep heh.

Even when they're asleep it isn't good enough. 180ms+ will get you killed a lot in the higher difficulties(hell act 2+) if you hit a rough champion pack. The amount of times I've been blown up or mortared due to THINKING I was safe is getting ridiculous and is making me want to stop playing altogether. I'm not even going to bother with Inferno as I know I'll just rage at it all the time. This game is really highlighting the fact that they need to establish an oceanic set of servers if they're going to continue with their online only mindset. 200ms is fine for WoW as the game play doesn't need that split second timing(well PVE doesn't anyway, I can't speak for PVP as I never did that while I played) but at times this game really needs that split second timing we just can't get when we have such high latency.

I know it's not good enough overall especially at higher levels but it is better than being at 300 - 400 all the time.

[Wishbone]

Read this on the interwebz ....

"Setting the TcpAckFrequency may improve your apparent ping but will not improve your actual network speed. If anything, it may make it worse by increasing the number of actual packets being transmitted by your machine for the same amount of data.

When a computer connects to another computer using TCP it performs what is known as the TCP Three-way Handshake. what happens is this:

1. Client computer sends a SYN (synchronize) packet to the server computer
2. Server computer sends a SYN-ACK (SYN-acknowledged) packet to the client computer
3. Client computer sends a final ACK (ACK acknowledged packet to the server computer.

Thus begins the TCP connection.

All these SYN, SYN-ACK, and ACK packets carry no actual data. The Windows network stack, since Windows 2000 has, by default, only responded to every other TCP SYN packet unless additional data packets are not received within a specific period of time (per RFC-1122). This reduces the total number of non-data packets that must be sent. Changing the referenced registry value to 1 will cause Windows to respond to every SYN packet, thus doubling the TCP overhead for a connection. While this will likely improve the "ping" rating you get in online games (since it takes a SYN packet less time to be ACKed) it will not increase the actual speeds of data transfer but reduce it. "

Makes sense to my untrained eye.

[yeapal]

Most people have bandwidth to spare these days. Latency however can never be spared.

[Wishbone]

Most people have bandwidth to spare these days. Latency however can never be spared.

That's the thing. Yes you'll lower your ping by lessening the TCP handshaking but your still using the same bandwidth so you'll actual throughput will not increase. A ping is only 32 bytes so it will move very fast. D3 game traffic will be allot more data transfer so performance will decrease massively over the same link.

Correct me if I'm wrong

[SaNE]

D3 game traffic will be allot more data transfer so performance will decrease massively over the same link.

Game traffic isn't large enough to be affected by the additional overheads caused by the modification.

[André Axe'm]

The handshake isn't the problem.
The problem is when the traffic is paused (Nagle's), because one side hasn't recieved the ACK from its previous packet (TCP Delayed Ack).

[Marius]

That still really doesn't explain how I noticed an improvement from 300-400 latency in Australian prime time down to 220 again using this.

My performance has actually measurable improved. Perhaps it's not for everyone, but it's something to try.

[Village idiot]

All this technical mumbo jumbo... I wish i was smarter in relation to all this stuff.

Suffice to say, i tried it and seems to work and improve my ping at the moment.

Im guessing that if i choose to revert later its as simple as deleting the dword i created in this this vid? Or will i break and kill everything?

[André Axe'm]

Apparently windows only send the Ack for every two packets or every 500ms.
Nagle's Algorithm tells the machine to hold all outgoing packets until it gets the Ack from its last sent packet.
So place these two thingamagigs on opposite sides of a client-server link and one stops sending data because it is waiting for an Ack, that won't be sent until another packet turns up. This other packet being the one on hold. So the two machines end up waiting for each other.

The video at the start of this thread only tells you how to get the Ack sent for every packet. (unless you found an MSMQ entry)
To disable Nagle's as well, add TCPNoDelay = 1, in the same place as the TcpAckFrequency = 1.

Yeah you can just delete the words if you added them.
If they already exist and you changed them, you should change them back to what they were.

[XViper]

Most people have bandwidth to spare these days. Latency however can never be spared.

That's the thing. Yes you'll lower your ping by lessening the TCP handshaking but your still using the same bandwidth so you'll actual throughput will not increase. A ping is only 32 bytes so it will move very fast. D3 game traffic will be allot more data transfer so performance will decrease massively over the same link.

What Wishbone is trying to say is: (Queue analogy)

You can run from one end of the room to another in a certain amount of time. (ping)
Taking your shoes off might make you complete that run in a faster time. (suggested registry tweak)
However if you're carrying a 50kg backpack (game data), your shoes really aren't going to make much of a difference. Infact the support your shoes give when carrying the backpack may actually be beneficial for your feet/safety.

Did I make any sense, or did that just sound completely retarded?