Wow lags since wotlk, time for me to figure out why

[dietro]

I'll try and be as brief as possible although there is alot of information to convey.

Since wotlk I've noticed a strange lag in the game, I actually first noticed it on the ptr before the expansion even released. I use the tcpackfrequency registry edit and have lowered my in-game latency by about 100ms, however I also refer to the quartz mod latency display and it consistantly shows me between 200ms and 500ms. I strongly feel that quartz is a more accurate picture of the latency that I'm getting.

Now I've taken about every step that I can think of so here is a quick list:

1. Updated all drivers and firmware and windows updates
2. Formatted my HD and reinstalled OS and game clean (have tried xp and vista)
3. Have opened all ports related to the game and verified they were open with PFPortchecker.
4. Optimized nic settings for wow, checksum offload disabled, large send disabled, tried every duplex setting.
5. Use both registry tweaks, tcpackfrequency and tcpnodelay.
6. Have tried comcast cable internet instead of my dsl.

My system should be more then enough to run this game, as a side note my fps are usually fine, 30fps in ulda 25 with high settings. Here are my specs:

Intel Core 2Duo E6750, 2.66ghz
4gigs ram (3.24 in xp)
geforce 9800gtx
Verizon dsl 5-6mb down/400kbs
westell 2210modem
linksys wrt54g router

Other people I play with havent noticed this, so I feel like its on my end. I've run traceroutes and for the most part they seem ok. It shows me roundtriping to the server I play on at 75ms. One thing though regarding the traceroutes; I dont really know how to read them. On the one hand I've read that only the last hop really matters, any spikes or packetdrops that arent passed on to later hops probably just indicates a turnaround issue or something to that effect, but on the other hand when blizzard techs in the tech forum read a traceroute they look, and comment, on the spikes and dropped packets. Now I'm not getting any packetloss, but I do show spikes throughout. Not on any particular hop either, these spikes could appear on any of the 17 hops it takes me to reach my server.

Thanks in advance for any insight anyone can shed on this. The lag really doesnt effect me at all in pve, but I've dusted myself off from s3 and have stepped back into the arena where it is very noticable.

[Jason09]

Is your Internet speed normal?

[dietro]

Originally Posted by Jason09

Is your Internet speed normal?

Seems pretty normal, just ran the speakeasy speed test and got 6mb down and 428kbps up.

Browsing is fine, webpages open quickly.

[dietro]

Here are a few screenshots of the quartz latency display, notice the in game latency with the registry edit in the top left corner looks good at ~80ms, but trust me the game is not running at that ms. Its much slower.







Here is a tracerts from Bellsouth DSL:

1 1 ms <1 ms <1 ms 192.168.1.1
2 27 ms 27 ms 27 ms 68.152.180.4
3 26 ms 27 ms 27 ms 68.152.250.213
4 33 ms 33 ms 32 ms ixc01jax-ge-1-0-7.bellsouth.net [205.152.70.146]
5 32 ms 33 ms 33 ms ixc00mia-pos-5-0.bellsouth.net [65.83.237.11]
6 65 ms 33 ms 33 ms axr01msy-so-7-3-0.bellsouth.net [65.83.237.18]
7 32 ms 32 ms 32 ms pxr00apx-ge-1-3-0.bellsouth.net [65.83.236.160]
8 34 ms 33 ms 32 ms 65.83.238.178
9 73 ms 77 ms 73 ms cr2.ormfl.ip.att.net [12.122.143.134]
10 73 ms 73 ms 73 ms cr1.attga.ip.att.net [12.122.5.142]
11 73 ms 73 ms 73 ms cr2.wswdc.ip.att.net [12.122.1.174]
12 73 ms 73 ms 73 ms cr2.n54ny.ip.att.net [12.122.3.37]
13 72 ms 73 ms * cr1.cb1ma.ip.att.net [12.122.31.126]
14 72 ms 73 ms 72 ms gar5.cb1ma.ip.att.net [12.122.145.29]
15 73 ms 73 ms 71 ms 12-122-254-14.attens.net [12.122.254.14]
16 75 ms 73 ms 76 ms mdf001c7613r0003-gig-10-1.bos1.attens.net

[dietro]

Another Tracert from Bellsouth DSL

1 1 ms <1 ms <1 ms 192.168.1.1
2 28 ms 26 ms 26 ms 68.152.180.4
3 27 ms 27 ms 31 ms 68.152.181.197
4 34 ms 33 ms 38 ms ixc01jax-ge-1-0-7.bellsouth.net [205.152.70.146]
5 32 ms 31 ms 31 ms ber01gnv-pos-1-0-0.bellsouth.net [65.83.239.129]
6 33 ms 33 ms 32 ms axr01msy-7-3-0.bellsouth.net [65.83.237.18]
7 34 ms 32 ms 32 ms pxr00ash-so-2-0-0.bellsouth.net [65.83.236.118]
8 31 ms 31 ms 31 ms 65.83.238.178
9 88 ms 98 ms 88 ms cr1.ormfl.ip.att.net [12.122.143.10]
10 92 ms 89 ms 89 ms cr1.hs1tx.ip.att.net [12.122.31.241]
11 89 ms 93 ms 89 ms cr2.santx.ip.att.net [12.122.30.137]
12 89 ms 88 ms 88 ms cr2.phmaz.ip.att.net [12.122.1.17]
13 88 ms 88 ms 88 ms cr1.la2ca.ip.att.net [12.122.31.189]
14 88 ms 88 ms 88 ms gar5.la2ca.ip.att.net [12.122.128.25]
15 91 ms 95 ms 89 ms 12.122.255.74
16 201 ms 215 ms 203 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.129.193.246]

And here is one from my new isp, comcast cable

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 8 ms 7 ms 7 ms te-9-2-sr02.southside.fl.jacksvil.comcast.net [68.86.171.197]
4 8 ms 7 ms 6 ms te-7-1-ar01.westside.fl.jacksvil.comcast.net [68.86.168.129]
5 9 ms 9 ms 9 ms te-7-2-ar01.southsiderdc.fl.jacksvil.comcast.net [68.86.168.126]
6 14 ms 16 ms 29 ms te-0-2-0-6-ar03.pompanobeach.fl.pompano.comcast.net [68.86.164.25]
7 15 ms 18 ms 14 ms pos-0-7-0-0-ar03.northdade.fl.pompano.comcast.net [68.86.164.5]
8 17 ms 16 ms 17 ms pos-0-3-0-0-cr01.miami.fl.ibone.comcast.net [68.86.91.221]
9 31 ms 31 ms 31 ms pos-2-3-0-0-cr01.atlanta.ga.ibone.comcast.net [68.86.85.193]
10 52 ms 53 ms 53 ms pos-1-12-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.85.157]
11 60 ms * 57 ms a190103.sandpiper.net [206.82.142.5]
12 51 ms * 53 ms Vlan6.icore1.DTX-Dallas.as6453.net [209.58.47.13]
13 51 ms 52 ms 52 ms 192.205.35.57
14 80 ms 78 ms 79 ms cr2.dlstx.ip.att.net [12.122.138.114]
15 78 ms 79 ms 79 ms cr1.attga.ip.att.net [12.122.28.173]
16 79 ms 78 ms 79 ms cr2.wswdc.ip.att.net [12.122.1.174]
17 79 ms 78 ms 78 ms cr2.n54ny.ip.att.net [12.122.3.37]
18 78 ms 78 ms 79 ms cr1.cb1ma.ip.att.net [12.122.31.126]
19 79 ms 77 ms 79 ms gar5.cb1ma.ip.att.net [12.122.145.33]
20 80 ms 80 ms 81 ms 12-122-254-14.attens.net [12.122.254.14]
21 80 ms 79 ms 79 ms mdf001c7613r0004-gig-12-1.bos1.attens.net [12.130.0.174]

Here is a comcast speed test: