TF2 server performance issues!!!

**DJ Ms. White** · 09-25-10, 11:35 PM

Originally Posted by Bunni

and btw if you couldnt tell from my posts or the server names, the new servers are up
CSS: GG -> 173.234.33.162:27040
CSS: Main ->173.234.33.162:27015
CSS: NoAwp ->173.234.33.162:27016
TF2: Main ->173.234.33.163:27015
TF2: Top5 ->173.234.33.163:27017
TF2: NoCrit ->173.234.33.163:27016
Dods: Main ->173.234.33.164:27015

The Game Servers links on the left need to be updated to reflect this.

**QuickLightning** · 09-26-10, 10:54 AM

Ouch... The new location doubles my ping from California. That might be it for me and our source servers as any large spikes will get me kicked.

C:\Users\xxxx>tracert 173.234.33.163

Tracing route to 173.234.33.163.rdns.ubiquityservers.com [173.234.33.163]
over a maximum of 30 hops:

1 8 ms 7 ms 7 ms 67.182.180.1
2 9 ms 7 ms 9 ms ge-4-9-ur09.sacramento.ca.sacra.comcast.net [68.
87.212.177]
3 10 ms 7 ms 7 ms te-9-1-ur08.sacramento.ca.sacra.comcast.net [68.
87.221.45]
4 7 ms 7 ms 7 ms te-1-2-ar01.sacramento.ca.sacra.comcast.net [68.
87.221.25]
5 8 ms 9 ms 7 ms 68.87.221.53
6 10 ms 9 ms 9 ms pos-0-1-0-0-cr01.sacramento.ca.ibone.comcast.net
[68.86.93.217]
7 18 ms 19 ms 17 ms pos-1-15-0-0-cr01.losangeles.ca.ibone.comcast.ne
t [68.86.85.86]
8 53 ms 53 ms 53 ms pos-0-12-0-0-cr01.dallas.tx.ibone.comcast.net [6
8.86.86.118]
9 74 ms 75 ms 73 ms pos-0-10-0-0-cr01.atlanta.ga.ibone.comcast.net [
68.86.86.130]
10 96 ms 95 ms 95 ms pos-3-13-0-0-cr01.chicago.il.ibone.comcast.net [
68.86.85.57]
11 95 ms 95 ms 95 ms pos-0-4-0-0-pe01.350ecermak.il.ibone.comcast.net
[68.86.86.162]
12 101 ms 107 ms 107 ms 66-208-229-50-ubr02b-muncie01-in.hfc.comcastbusi
ness.net [66.208.229.50]
13 101 ms 99 ms 99 ms xe0-cdn.cust.ord01.mzima.net [72.37.148.138]
14 96 ms 96 ms 97 ms 173.234.33.163.rdns.ubiquityservers.com [173.234

**Bunni** · 09-26-10, 11:28 AM

Originally Posted by QuickLightning

Ouch... The new location doubles my ping from California. That might be it for me and our source servers as any large spikes will get me kicked.

C:\Users\xxxx>tracert 173.234.33.163

Tracing route to 173.234.33.163.rdns.ubiquityservers.com [173.234.33.163]
over a maximum of 30 hops:

1 8 ms 7 ms 7 ms 67.182.180.1
2 9 ms 7 ms 9 ms ge-4-9-ur09.sacramento.ca.sacra.comcast.net [68.
87.212.177]
3 10 ms 7 ms 7 ms te-9-1-ur08.sacramento.ca.sacra.comcast.net [68.
87.221.45]
4 7 ms 7 ms 7 ms te-1-2-ar01.sacramento.ca.sacra.comcast.net [68.
87.221.25]
5 8 ms 9 ms 7 ms 68.87.221.53
6 10 ms 9 ms 9 ms pos-0-1-0-0-cr01.sacramento.ca.ibone.comcast.net
[68.86.93.217]
7 18 ms 19 ms 17 ms pos-1-15-0-0-cr01.losangeles.ca.ibone.comcast.ne
t [68.86.85.86]
8 53 ms 53 ms 53 ms pos-0-12-0-0-cr01.dallas.tx.ibone.comcast.net [6
8.86.86.118]
9 74 ms 75 ms 73 ms pos-0-10-0-0-cr01.atlanta.ga.ibone.comcast.net [
68.86.86.130]
10 96 ms 95 ms 95 ms pos-3-13-0-0-cr01.chicago.il.ibone.comcast.net [
68.86.85.57]
11 95 ms 95 ms 95 ms pos-0-4-0-0-pe01.350ecermak.il.ibone.comcast.net
[68.86.86.162]
12 101 ms 107 ms 107 ms 66-208-229-50-ubr02b-muncie01-in.hfc.comcastbusi
ness.net [66.208.229.50]
13 101 ms 99 ms 99 ms xe0-cdn.cust.ord01.mzima.net [72.37.148.138]
14 96 ms 96 ms 97 ms 173.234.33.163.rdns.ubiquityservers.com [173.234

call up your ISP, and point out that bizarre route, they'll unbotch it.

**...bigdog...** · 09-26-10, 01:37 PM

Originally Posted by jabberwock

Any news on the possible migration?

nothing "possible" about it. It's a done deal. Hypernia is shutting down the facility our current source server is at, and migrating us to a higher end machine in chicago.

I just posted my trace to the IP in tracert's. run some and see how you can expect to connect.

Faster machine. Crap load more ram for some reason. bigger HD. maybe things will improve.

**...bigdog...** · 09-26-10, 01:38 PM

Originally Posted by QuickLightning

Ouch... The new location doubles my ping from California. That might be it for me and our source servers as any large spikes will get me kicked.

our ping kick limit is well over 100ms, and you have to have a sustained ping above the kick limit for.... 30s I believe?

**QuickLightning** · 09-26-10, 02:35 PM

Originally Posted by ...bigdog...

our ping kick limit is well over 100ms, and you have to have a sustained ping above the kick limit for.... 30s I believe?

My understanding was what we had previously was a 150ms ping kick limit and it scanned all latency every 30 (or 60) seconds. If 1 scan came up over the limit, it logs it, if two consecutive scans come up over the limit, you get kicked. And our limit is ~150 or so, right? Ping did not have to be sustained, but just be at that level when the server scans it. Do correct me if I am wrong on this though.

So I would just have to have 2 unlucky spikes. I would coast up to the 90s or low hundreds occasionally with my former 50-60 ping previously so it does not seem that unlikely.

I'm going to call up comcast and see if they can fix the routing though. If I can just get them to route me north rather than to Georgia, I'll be golden.

**~~insanegammer109~~** · 09-26-10, 02:38 PM

Originally Posted by QuickLightning

My understanding was what we had previously was a 150ms ping kick limit and it scanned all latency every 30 (or 60) seconds. If 1 scan came up over the limit, it logs it, if two consecutive scans come up over the limit, you get kicked. And our limit is ~150 or so, right? Ping did not have to be sustained, but just be at that level when the server scans it. Do correct me if I am wrong on this though.

So I would just have to have 2 unlucky spikes. I would coast up to the 90s or low hundreds occasionally with my former 50-60 ping previously so it does not seem that unlikely.

I'm going to call up comcast and see if they can fix the routing though. If I can just get them to route me north rather than to Georgia, I'll be golden.

Correct, That is how it works except if you are a reservist then you won't get kicked.