Author Topic: Lag on EV1 Servers? (Read 5727 times)

jitspoe · « **on:** March 26, 2007, 12:46:45 AM »

Wade just sub-leased an EV1 server for his gM clan, and several people have been complaining about lag spikes. What's weird is that I personally have not had any issues. My netgraph is almost perfectly flat on the bottom. At first I thought it might have been a CPU issue, so I cranked up the priority on it, but people are still getting serious lag issues. Since I'm not, it can't be that. It has to be some kind of routing issue. If you're one of the people having issues, could you post a tracert? Do this:

Start|Run
cmd

Then when the black "DOS" box pops up, type:
tracert dplogin.com > c:\test.txt

Give it a few minutes to finish, then open c:\test.txt in notepad and paste the results. It should look something like this:

Code: [Select]

Tracing route to dplogin.com [216.127.68.86]

over a maximum of 30 hops:



  1    <1 ms    <1 ms    <1 ms  192.168.0.1 

  2    20 ms     7 ms     9 ms  10.203.96.1 

  3    15 ms    10 ms     5 ms  24.93.65.165 

  4    10 ms     9 ms    10 ms  srp0-0.chrlncsa-rtr4.carolina.rr.com [24.93.67.175] 

  5     9 ms    11 ms    31 ms  pos2-0.chrlncsa-rtr1.southeast.rr.com [24.93.66.238] 

  6    16 ms    15 ms    16 ms  son1-0-3.rlghncrdc-rtr3.nc.rr.com [24.93.64.85] 

  7    13 ms    15 ms    15 ms  son1-1-1.chrlncsa-rtr6.southeast.rr.com [24.93.64.17] 

  8    13 ms    16 ms    15 ms  pop1-cha-P7-0.atdn.net [66.185.138.69] 

  9    16 ms    16 ms    16 ms  bb1-cha-P3-0.atdn.net [66.185.138.64] 

 10    20 ms    19 ms    24 ms  bb1-atm-P6-0.atdn.net [66.185.152.182] 

 11    23 ms    19 ms    20 ms  pop1-atm-P1-0.atdn.net [66.185.147.193] 

 12    19 ms    19 ms    20 ms  so-5-2-0.mpr1.atl6.us.above.net [209.249.119.241] 

 13    41 ms    39 ms    41 ms  so-3-3-0.mpr2.iah1.us.above.net [64.125.29.66] 

 14    43 ms    41 ms    43 ms  so0-0-0.mpr3.iah1.us.above.net [64.125.26.13] 

 15    44 ms    43 ms    44 ms  289.ge-3-2-1.mpr1.iah1.us.above.net [216.200.251.26] 

 16    44 ms    43 ms    44 ms  ivhou-207-218-245-27.ev1servers.net [207.218.245.27] 

 17    43 ms    41 ms    43 ms  ivhou-207-218-245-124.ev1servers.net [207.218.245.124] 

 18    42 ms    43 ms    43 ms  dplogin.com [216.127.68.86] 



Trace complete.

Screenshots of netgraphs could also be helpful (type "netgraph 1" at the console to enable the network graph).

wade · « **Reply #1 on:** March 26, 2007, 04:24:56 AM »

Tracing route to dplogin.com [216.127.68.86]

over a maximum of 30 hops:

1 3 ms <1 ms <1 ms 121.121.12.212

2 25 ms 10 ms 9 ms d192-24-1-120.try.wideopenwest.com [24.192.120.1]

3 12 ms 8 ms 9 ms 172.31.12.222

4 17 ms 27 ms 46 ms 12.119.243.153

5 29 ms 67 ms 15 ms gbr2-p30.dtrmi.ip.att.net [12.123.208.62]

6 51 ms 16 ms 21 ms tbr2-cl18.cgcil.ip.att.net [12.122.10.134]

7 22 ms 17 ms 15 ms ggr3-ge110.cgcil.ip.att.net [12.123.4.253]

8 27 ms 16 ms 15 ms p16-0.att.chcgil06.us.bb.gin.ntt.net [192.205.32.194]

9 47 ms 50 ms 39 ms p64-2-2-0.r21.dllstx09.us.bb.gin.ntt.net [129.250.2.22]

10 69 ms 49 ms 51 ms p64-1-1-0.r21.hstntx01.us.bb.gin.ntt.net [129.250.4.69]

11 46 ms 57 ms 45 ms xe-4-1.r04.hstntx01.us.bb.gin.ntt.net [129.250.2.231]

12 145 ms 47 ms 45 ms ge-4.ev1.hstntx01.us.bb.gin.ntt.net [129.250.10.142]

13 61 ms 46 ms 46 ms ivhou-207-218-245-29.ev1servers.net [207.218.245.29]

14 45 ms 44 ms 46 ms ivhou-207-218-245-124.ev1servers.net [207.218.245.124]

15 85 ms 50 ms 68 ms dplogin.com [216.127.68.86]

Trace complete.

T3RR0R15T · « **Reply #2 on:** March 26, 2007, 05:30:18 AM »

Routenverfolgung zu dplogin.com [216.127.68.86] ber maximal 30 Abschnitte:

1 <1 ms <1 ms <1 ms fritz.fonwlan.box [192.168.178.1]

2 8 ms 8 ms 7 ms 217.0.116.186

3 8 ms 8 ms 8 ms 217.0.75.150

4 26 ms 26 ms 26 ms isp-linx-gw13-o.nmc-m.dtag.de [217.239.38.241]

5 27 ms 26 ms 26 ms 62.156.139.254

6 27 ms 27 ms 26 ms xe-0-2-0.r23.londen03.uk.bb.gin.ntt.net [129.250.2.66]

7 * * 104 ms p64-1-0-0.r20.nycmny01.us.bb.gin.ntt.net [129.250.3.254]

8 105 ms 104 ms 104 ms as-0.r21.asbnva01.us.bb.gin.ntt.net [129.250.2.9]

9 135 ms 137 ms 136 ms p64-1-1-0.r20.dllstx09.us.bb.gin.ntt.net [129.250.5.24]

10 141 ms 141 ms 142 ms p64-1-0-0.r20.hstntx01.us.bb.gin.ntt.net [129.250.4.71]

11 141 ms 140 ms 141 ms xe-4-1.r03.hstntx01.us.bb.gin.ntt.net [129.250.2.229]

12 140 ms 139 ms 139 ms ge-1.ev1.hstntx01.us.bb.gin.ntt.net [129.250.10.70]

13 135 ms 135 ms 135 ms ivhou-207-218-245-29.ev1servers.net [207.218.245.29]

14 135 ms 136 ms 135 ms ivhou-207-218-245-124.ev1servers.net [207.218.245.124]

15 136 ms 136 ms 136 ms dplogin.com [216.127.68.86]

Ablaufverfolgung beendet.

XtremeBain · « **Reply #3 on:** March 26, 2007, 05:55:44 AM »

Looks like it's happening on the NTT network. My connection is routing through the TimeWarner network and I haven't experienced any of these problems. From previous experience, the network engineers like to see the reverse trace routes (from dplogin.com -> clients) so it might be a good idea to run those off from your server as well.

KnacK · « **Reply #4 on:** March 26, 2007, 05:57:12 AM »

wade and terrorist both share ntt.net

bitmate · « **Reply #5 on:** March 26, 2007, 06:36:01 AM »

I'm going through the NTT network as well, but for me the netgraph is at the bottom line all of the time.
Can't be NTT's network

Code: [Select]

Routenverfolgung zu dplogin.com [216.127.68.86]  ber maximal 30 Abschnitte:



  1     3 ms    <1 ms    <1 ms  fritz.fon.box [192.168.178.1] 

  2     *        *        *     Zeitberschreitung der Anforderung.

  3    52 ms    52 ms    52 ms  217.0.76.50 

  4    67 ms    68 ms    66 ms  isp-linx-gw13-o.nmc-m.dtag.de [217.239.38.241] 

  5    66 ms    69 ms    66 ms  62.156.139.254 

  6    68 ms    67 ms    68 ms  xe-0-2-0.r23.londen03.uk.bb.gin.ntt.net [129.250.2.66] 

  7   142 ms   147 ms   142 ms  p64-1-0-0.r20.nycmny01.us.bb.gin.ntt.net [129.250.3.254] 

  8   143 ms   141 ms   142 ms  as-0.r21.asbnva01.us.bb.gin.ntt.net [129.250.2.9] 

  9   174 ms   173 ms   173 ms  p64-1-1-0.r20.dllstx09.us.bb.gin.ntt.net [129.250.5.24] 

 10   181 ms   180 ms   179 ms  p64-1-0-0.r20.hstntx01.us.bb.gin.ntt.net [129.250.4.71] 

 11   179 ms   177 ms   192 ms  xe-4-1.r03.hstntx01.us.bb.gin.ntt.net [129.250.2.229] 

 12   176 ms   178 ms   176 ms  ge-1.ev1.hstntx01.us.bb.gin.ntt.net [129.250.10.70] 

 13   172 ms   173 ms   174 ms  ivhou-207-218-245-27.ev1servers.net [207.218.245.27] 

 14   174 ms   173 ms   174 ms  ivhou-207-218-245-124.ev1servers.net [207.218.245.124] 

 15   174 ms   173 ms   174 ms  dplogin.com [216.127.68.86] 



Ablaufverfolgung beendet.

b00nlander · « **Reply #6 on:** March 26, 2007, 07:12:28 AM »

Quote from: KnacK on March 26, 2007, 05:57:12 AM

wade and terrorist both share ntt.net

- traces don't show any lag on either of them, though (Terror is european, so his ping increases when switching backbones from EU to US)
- maybe people should check for netgraph trouble indicating packetloss, which is a lot more often a cause to the "laggy game" feeling, and only run tracert if the netgraph shows a bunch of black spikes

jitspoe · « **Reply #7 on:** March 26, 2007, 12:52:41 PM »

I don't think wade was having any serious lag issues. Kilo and DirtyTaco did, though. I'm not sure who else.

Eiii · « **Reply #8 on:** March 26, 2007, 03:14:40 PM »

Quote from: b00nlander on March 26, 2007, 07:12:28 AM

- maybe people should check for netgraph trouble indicating packetloss, which is a lot more often a cause to the "laggy game" feeling, and only run tracert if the netgraph shows a bunch of black spikes

Black spikes = packetloss

I, too, go through NTT, and have no lag.

KiLo · « **Reply #9 on:** March 26, 2007, 09:46:06 PM »

Quote from: jitspoe on March 26, 2007, 12:52:41 PM

I don't think wade was having any serious lag issues. Kilo and DirtyTaco did, though. I'm not sure who else.

You're darn straight that I was have lag issues.

I don't know about the netgraphs and all that stuff but I never had a lag problem on EV1 Servers up until a couple days ago.

Edit: I'm getting tired of this swear filter. Other users aren't getting the full affect of my posts by it being there.

jitspoe · « **Reply #10 on:** March 27, 2007, 02:30:41 AM »

Kaos was complaining the most about the lag. He sent me this screenshot. The framerate makes me a bit suspect that he might be having other issues, though. Hopefully he can post his tracert here.

Another thing that might be helpful is to type "cl_showmiss 1" at the console. That will show prediction misses.

Eiii · « **Reply #11 on:** March 27, 2007, 03:10:06 AM »

How can you even have a framerate that low?

With that much lag, I wouldn't be surprised if it was something on his end. A bad connection, or something.

KnacK · « **Reply #12 on:** March 27, 2007, 04:59:26 AM »

Iowuld say that he does have other issues. Even I keep a framerate above 50 to 60.

XtremeBain · « **Reply #13 on:** March 27, 2007, 08:26:43 AM »

Make sure he doesn't have cl_locknetfps set at 1, that will help isolate network/system related problems.

Kaos · « **Reply #14 on:** March 27, 2007, 03:30:23 PM »

Tracing route to dplogin.com [216.127.68.86]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms dslrouter [192.168.1.1]
2 30 ms 29 ms 30 ms 10.9.41.1
3 29 ms 29 ms 30 ms so-0-3-2-0.CORE-RTR1.BOS.verizon-gni.net [130.81
.4.237]
4 30 ms 30 ms 30 ms so-0-2-0-0.BB-RTR1.BOS.verizon-gni.net [130.81.2
0.84]
5 40 ms 41 ms 41 ms so-6-2-0-0.BB-RTR2.NY325.verizon-gni.net [130.81
.19.70]
6 134 ms 37 ms 39 ms so-7-0-0-0.PEER-RTR1.NY111.verizon-gni.net [130.
81.17.131]
7 40 ms 38 ms 38 ms so-0-3-1.mpr2.lga5.us.above.net [64.125.13.33]
8 44 ms 44 ms 44 ms so-1-0-0.mpr2.iad1.us.above.net [64.125.28.65]
9 46 ms 49 ms 46 ms so-1-0-0.mpr2.dca2.us.above.net [64.125.27.210]

10 87 ms 80 ms 75 ms so-2-3-0.cr2.dfw2.us.above.net [64.125.29.13]
11 80 ms 82 ms 82 ms so-4-1-0.mpr2.iah1.us.above.net [64.125.29.17]
12 93 ms 82 ms 82 ms so0-0-0.mpr3.iah1.us.above.net [64.125.26.13]
13 81 ms 79 ms 80 ms 289.ge-3-2-1.mpr1.iah1.us.above.net [216.200.251
.26]
14 78 ms 80 ms 80 ms ivhou-207-218-245-28.ev1servers.net [207.218.245
.28]
15 78 ms 79 ms 80 ms ivhou-207-218-245-124.ev1servers.net [207.218.24
5.124]
16 81 ms 80 ms 79 ms dplogin.com [216.127.68.86]

Trace complete.

Quote from: XtremeBain on March 27, 2007, 08:26:43 AM

Make sure he doesn't have cl_locknetfps set at 1, that will help isolate network/system related problems.

its set 0 idk how i have that low of fps and the much lagg with the a hugh packet loss idk how this happened but i jus restarted jy comp after jit asked me about cl_locknetfps idk if it changed cuz i had my comp on for a week so idk

Quote from: eiii on March 27, 2007, 03:10:06 AM

How can you even have a framerate that low?

With that much lag, I wouldn't be surprised if it was something on his end. A bad connection, or something.

i have dsl never ever had it that low before and i have serveral other sshots with the same looks as the first

Eiii · « **Reply #15 on:** March 27, 2007, 04:58:18 PM »

Are you plugged directly into the DSL, or is it on a network. Wireless? Firewall?

Kaos · « **Reply #16 on:** March 27, 2007, 05:42:57 PM »

Quote from: eiii on March 27, 2007, 04:58:18 PM

Are you plugged directly into the DSL, or is it on a network. Wireless? Firewall?

not wireless no firewalls idk wat u mean by network

Zorchenhimer · « **Reply #17 on:** March 27, 2007, 07:54:13 PM »

Is your computer plugged directly into a modem? Or are you connected to a router?

KiLo · « **Reply #18 on:** March 27, 2007, 08:03:04 PM »

I experienced kaos's problem about an hour ago on the ]pS[ Clan Server. I was playing and I had 50-60 fps then suddenly it dropped to 3 fps. I quit the game and then restarted and it was fine.

Eiii · « **Reply #19 on:** March 27, 2007, 08:16:19 PM »

He's talking about network lag, not graphic lag. Yours is a different problem entirely, probably something on your end.