This video improved my latency considerably

[Marius]

So all this week I've been struggling with a 350-400 ping.

Following the instructions in this video reduced it to a stable 220 again.

Note I also had to reset my router after the computer restart to reconnect to the net.

[youtube]5rhWeL4L_pI&feature=related[/youtube]

[yeapal]

Thanks for that, you're awesome!

I'm now getting pings of 250ish during peak US times where I'd normally get pings of 350-400.

I'll give it a shot tonight during peak AU times and see if it's any better again.

[CelticAngel82]

well ****, isnt that what i've been trying to say all week?
hope you made a restore point.

[Marius]

I did credit you in the review topic in the news section...

But you didn't say 'how' to do it, so this video does that.

[André Axe'm]

right...

So blizzard really can't be bothered writing good netcode then?

[Mekon]

So blizzard really can't be bothered writing good netcode then?

Less of a Blizzard thing and more of an increasingly irrelevant TCP/IP stack optimisation.

Nagle's Algorithm is designed to reduce bandwidth at the expense of latency - in today's high bandwidth, time-sensitive environments, a few extra packets flying around aren't such a big deal.

[lucassot]

I've noticed ping going up while lots of people are on the servers then by our peak time it's back to 210 - 220. Will try this tonight and see how I go. Thanks for the post.

[diamondd]

So blizzard really can't be bothered writing good netcode then?

Less of a Blizzard thing and more of an increasingly irrelevant TCP/IP stack optimisation.

Nagle's Algorithm is designed to reduce bandwidth at the expense of latency - in today's high bandwidth, time-sensitive environments, a few extra packets flying around aren't such a big deal.

mmm, yeah but its a similar thing to writing memory inefficient software.. just because RAM is abundant these days doesn't make it OK.

Ideally you could set this on a per-application basis.

[Sathias]

I'm still working on whether its possible to use GON's WoW gateway to connect to Diablo 3 and get an improvement that way, from the research I've done the sticking point seems to be that D3 uses UDF rather than TCP, and Putty does not handle UDF data. If I manage to work something out I will post about it

[Village idiot]

Nice find. I will be trying this tomorrow for sure.

[CelticAngel82]

Soooooo.......... how's everyone who's tried it, finding it then? Good reports so far from the ones who have spoken to me about it.

[Marius]

So far so good, but still vulnerable to heavy traffic/routing issues. I'm trying a ping tunneling service on top to try and stabilize things.

Since there's three points at which a connection can falter:

1. Your router.
2. En route.
3. Blizzard's servers.

The tweaks here address 1, a tunnel addresses 2, can't do much about 3. But by addressing the first two it seems to help get it stable. Blizzard is also adding capability to their servers.

[lucassot]

Didn't work for me My ping actually went up after I tried it heh. Ah well!

[Giblet1]

Tried it, didn't do anything, removed it. Ah well, if only we had local servers

[Marius]

What's your normal ping? If you're getting around 210-230 normally, there's probably not much you can do beyond there.

If not, have you tried anything else to improve latency?

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