longstreet
join:2004-11-14
Plano, TX
2 edits | reply to dietro
Re: High Latency in WoW, North Florida to Boston
Did you recently change any hardware, do you use wireless, or upgrade your OS (or receive an update for it?)
this
»What your average MS response time in WoW?
Might solve your problem.
I went from 300 ish to 75 (even in Dalaran)
Be aware though, it will affect your max throughput in exchange for better latency. |
|
dietro
join:2009-05-29
Jacksonville, FL
2 edits | Have I changed my hardware? I've changed everything! lol
But only in an attempt to correct the latency, I had done nothing before this issue began (except to download the wotlk patch)
Here are some things I have tried
Steps that I have taken to improve my latency:
Run traceroutes
Used programs like Wireshark, Pingplotter, 3dtraceroute, or the Command prompt
Optimize network
Used programs like DrTcp
Manually changed MTU, Enable or disable QoS
Change NIC settings: checksum offload disable, change duplex settings, large send offload disable, disable power management.
Open ports. 3724 tcp, 1119 tcp, 3724 udp, 6112 tcp, 6881-6999 tcp and ports to DNS usually 53 udp I think. .
Check that ports are open with PFPortChecker
Update firmware/drivers
Motherboard
Nic
Sound/Video
OS
Modem
Router
Edit Registry
TcpAckFrequency (this lowered my in-game latency dramatically on both xp and vista, seemed to improve character response time to mouse/keyboard inputs but did nothing for other latency related issues and didnt alter my Quartz latency timer at all)
TcpNoDelay
Change hardware
Took router out (connect directly to modem)
Different router
Different modem
Different NIC
Different PC
Other steps taken
Checked for VIruses
Delete WTF, WDB, interface folders
Clean up and defrag hard drive
Reinstall operating system, or install a different operating system
Reinstall game
Side-by-side ISP test (both cable and dsl)
Contacted both ISPs |
|
longstreet
join:2004-11-14
Plano, TX
4 edits | It sounds like you're being limited by physical distance and number of hops. It's been some time since I had my theory classes in TCP/IP (> a decade), but if you've done all that . . . i'm stumped to come up with another solution.
Your connection isn't saturated is it? When you test, i'd try testing with a TCP ping / trace program.
Regular windows ping and iirc, tracert are powered by UDP, which isn't reliable when it comes to packet delivery.
Are you seeing packet loss with your dsl reports connection tests?
In any event, the problem isn't wow and likely isn't the servers and connections they are hosted on. |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
 ·Pacific Bell - SBC
| said by longstreet  :In any event, the problem isn't wow and likely isn't the servers and connections they are hosted on. He's got good latency in his own transit networks (Bellsouth and Comcast), so the trouble isn't likely between his equipment and the peer connection to AT&T.
I was reminded by a network guru who knows more than I that routes aren't always symmetrical. The forward path, which is shown by his trace route may not reflect the return path, which can only be seen by running a trace route from the game server back to his connection. If the return path is taking the long way home, he will see weird latency issues. To a great extent, that return path is under Blizzard's control.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
longstreet
join:2004-11-14
Plano, TX
1 edit | Maybe my memory fails me. The routes are almost always different. Can you explain how one of blizzards servers (likely co-located) can 'choose' a path home?
Even if it really is ICMP, it's exactly like UDP in terms of it's reliability.
edit :
Found this
quote:
Many commonly-used network utilities are based on ICMP messages. The traceroute command is implemented by transmitting UDP datagrams with specially set IP TTL header fields, and looking for ICMP Time to live exceeded in transit (above) and "Destination unreachable" messages generated in response. The related ping utility is implemented using the ICMP "Echo request" and "Echo reply" messages.
I guess my memory is good after all. |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
·Pacific Bell - SBC
| said by longstreet :Maybe my memory fails me. The routes are almost always different. Can you explain how one of blizzards servers (likely co-located) can 'choose' a path home? BGP, which I admit to know not a lot about. Something about how networks use BGP to control packet egress (and probably ingress, as well). I expect that it is a cooperative effort for both source and destination. And likely not easy to tweak for latency performance.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
