Jump to content

WEST RUBBERBAND THREAD


stutters

Recommended Posts

so here we go. apparently west has been "rubber banding" over the last week while i was gone, and i've defintely noticed it the last two nights. i'm not really to sure where to start with this. there haven't been any significant changes to the server, and there hasn't been a steam server update lately. i ran a ping plot last night, and nothing too out of place:

 

Target Name: 72-37-147-22.la.aim2game.com

IP: 72.37.147.22

Date/Time: 2/14/2006 7:24:23 AM to 2/14/2006 7:26:02 AM

 

Hop Sent Err PL% Min Max Avg Host Name / [iP]

1 100 0 0.0 1 2 1 ppp-71-138-147-222.dsl.pltn13.pacbell.net [71.138.147.222]

2 100 0 0.0 8 92 18 bras10-l0.pltnca.sbcglobal.net [151.164.184.66]

3 100 0 0.0 7 9 8 dist1-vlan50.pltn13.pbi.net [64.164.97.66]

4 100 0 0.0 7 220 12 bb1-g3-0.pltnca.sbcglobal.net [151.164.43.54]

5 100 0 0.0 9 210 23 bb1-p4-0.crsfca.sbcglobal.net [151.164.41.5]

6 100 0 0.0 9 174 18 ex1-p3-0.eqsjca.sbcglobal.net [151.164.41.101]

7 100 0 0.0 10 24 15 eqix-peer.sjc01.mzima.net [206.223.116.62]

8 100 0 0.0 9 11 10 pos1-0.cr01.sjc02.mzima.net [64.235.224.205]

9 100 0 0.0 24 38 29 pos4-0.cr01.lax02.mzima.net [64.235.224.81]

10 100 0 0.0 24 225 30 ge1-1.ar01.lax02.mzima.net [64.235.224.214]

11 100 0 0.0 24 28 24 72-37-147-22.la.aim2game.com [72.37.147.22]

 

the max column has a few eyeraisers, but no packet loss, and a reasonable average. then again, it did run overnight. like i said, i'm not too sure where to start, so if you notice it, please post:

 

time:

map:

how many current players:

how many total players (type status):

 

i'll make sure the server is restarted every morning, but last night the total player count was just above 2000...which is a days worth of traffic. the only thing i can think is to lower the overall server maxrate, but it's at 25000 which is typical. i'm open to ideas...

Link to comment
Share on other sites

did you run that ping plot laz?

 

 

Um ... no. But I have a good excuse! I stayed on with one eye open until 430 in the morning and kept it bumpin. But then I was so tired I forgot.

 

Farmer : Rubberbanding/Snap-back lag:

When everything is running smoothly most of the time, then all of a sudden one of two things happen:

either everyone freezes for 1/2 second, OR , You "lose" 1/2 second of time. Like you run around a corner and pull out your rifle, then suddenly your back behind the corner with your pistol still out.

Link to comment
Share on other sites

nasty again tonite.

 

stats via hlsw:

20:22:46

CPU In Out Uptime Users FPS Players

46.00 62078.45 139067.53 769 36 167.20 24

 

20:37:57

CPU In Out Uptime Users FPS Players

59.00 88495.89 161373.38 784 37 167.06 22

 

ping plot sample 1:

Target Name: 72-37-147-22.la.aim2game.com

IP: 72.37.147.22

Date/Time: 2/14/2006 8:23:16 PM to 2/14/2006 8:24:55 PM

 

Hop Sent Err PL% Min Max Avg Host Name / [iP]

1 100 0 0.0 1 1 1 ppp-71-138-147-222.dsl.pltn13.pacbell.net [71.138.147.222]

2 100 0 0.0 8 91 11 bras10-l0.pltnca.sbcglobal.net [151.164.184.66]

3 100 0 0.0 7 15 8 dist1-vlan50.pltn13.pbi.net [64.164.97.66]

4 100 0 0.0 7 187 14 bb1-g3-0.pltnca.sbcglobal.net [151.164.43.54]

5 100 0 0.0 9 205 20 bb1-p4-0.crsfca.sbcglobal.net [151.164.41.5]

6 100 0 0.0 9 192 24 ex1-p3-0.eqsjca.sbcglobal.net [151.164.41.101]

7 100 0 0.0 10 23 15 eqix-peer.sjc01.mzima.net [206.223.116.62]

8 100 0 0.0 9 12 10 pos1-0.cr01.sjc02.mzima.net [64.235.224.205]

9 100 0 0.0 23 41 29 pos4-0.cr01.lax02.mzima.net [64.235.224.81]

10 100 0 0.0 24 234 28 ge1-1.ar01.lax02.mzima.net [64.235.224.214]

11 100 0 0.0 24 25 24 72-37-147-22.la.aim2game.com [72.37.147.22]

 

ping plot sample 2:

Target Name: 72-37-147-22.la.aim2game.com

IP: 72.37.147.22

Date/Time: 2/14/2006 8:34:40 PM to 2/14/2006 8:36:19 PM

 

Hop Sent Err PL% Min Max Avg Host Name / [iP]

1 100 0 0.0 1 1 1 ppp-71-138-147-222.dsl.pltn13.pacbell.net [71.138.147.222]

2 100 0 0.0 9 70 14 bras10-l0.pltnca.sbcglobal.net [151.164.184.66]

3 100 0 0.0 7 25 8 dist1-vlan50.pltn13.pbi.net [64.164.97.66]

4 100 0 0.0 7 200 19 bb1-g3-0.pltnca.sbcglobal.net [151.164.43.54]

5 100 0 0.0 9 218 19 bb1-p4-0.crsfca.sbcglobal.net [151.164.41.5]

6 100 0 0.0 9 190 18 ex1-p3-0.eqsjca.sbcglobal.net [151.164.41.101]

7 100 0 0.0 10 29 15 eqix-peer.sjc01.mzima.net [206.223.116.62]

8 100 0 0.0 9 18 10 pos1-0.cr01.sjc02.mzima.net [64.235.224.205]

9 100 1 1.0 23 43 29 pos4-0.cr01.lax02.mzima.net [64.235.224.81]

10 100 0 0.0 23 197 28 ge1-1.ar01.lax02.mzima.net [64.235.224.214]

11 100 0 0.0 24 32 24 72-37-147-22.la.aim2game.com [72.37.147.22]

 

 

end of demo shows "rubber band"

 

 

let's keep this on the hush/hush with the pubbers, no need to draw bad focus on things we're working to fix :peace:

Link to comment
Share on other sites

Member

ge1-1.ar01.lax02.mzima.net

Is bad for me when i run its not upto 100 but I am getting bad spikes from it all other nodes are at 20-30 ms or lower and this one bounces from 20-60. Anyone still use neotrace? its cool being able to pull up satelite photos. of the addy u trace.

Edited by FORZ
Link to comment
Share on other sites

Member

Target Name: 72-37-147-22.la.aim2game.com

IP: 72.37.147.22

Date/Time: 2/17/2006 8:07:16 PM to 2/17/2006 8:08:01 PM

 

1 62 ms 10 ms 10 ms 10 ms 10 ms 10 ms 10 ms 10 ms 10 ms 9 ms [68.123.1.254]

2 82 ms 11 ms 10 ms 10 ms 10 ms 10 ms 10 ms 10 ms 10 ms 10 ms dist1-vlan50.skt2ca.sbcglobal.net [68.120.211.66]

3 84 ms 11 ms 10 ms 121 ms 10 ms 11 ms 10 ms 10 ms 10 ms 13 ms bb2-g1-3-0.skt2ca.sbcglobal.net [68.120.211.228]

4 91 ms 12 ms 13 ms 144 ms 12 ms 12 ms 14 ms 12 ms 12 ms 13 ms bb1-p10-2.crscca.sbcglobal.net [151.164.191.241]

5 94 ms 13 ms 13 ms 13 ms 13 ms 13 ms 13 ms 13 ms 59 ms 13 ms ex2-p9-0.pxpaca.sbcglobal.net [151.164.243.47]

6 96 ms 13 ms 13 ms 13 ms 14 ms 13 ms 13 ms 13 ms 14 ms 13 ms paix.pao01.mzima.net [198.32.176.38]

7 118 ms 29 ms 29 ms 32 ms 33 ms 35 ms 36 ms 38 ms 39 ms 27 ms pos4-0.cr01.lax02.mzima.net [64.235.224.81]

8 88 ms 32 ms 27 ms * 27 ms 26 ms 27 ms 27 ms 27 ms 27 ms ge1-1.ar01.lax02.mzima.net [64.235.224.214]

9 63 ms 26 ms 26 ms 25 ms 27 ms 25 ms 26 ms 25 ms * 25 ms 72-37-147-22.la.aim2game.com [72.37.147.22]

 

Ping statistics for 72-37-147-22.la.aim2game.com

Packets: Sent = 10, Received = 9, Lost = 1 (10.0%)

Round Trip Times: Minimum = 25ms, Maximum = 63ms, Average = 29ms

 

 

Target Name: 72-37-147-22.la.aim2game.com

IP: 72.37.147.22

Date/Time: 2/17/2006 8:17:15 PM to 2/17/2006 8:17:37 PM

 

1 10 ms 9 ms 9 ms 9 ms 10 ms 10 ms 10 ms 10 ms 10 ms 10 ms [68.123.1.254]

2 10 ms 10 ms 11 ms 11 ms 10 ms 10 ms 10 ms 10 ms 11 ms 9 ms dist1-vlan50.skt2ca.sbcglobal.net [68.120.211.66]

3 10 ms 10 ms 10 ms 11 ms 161 ms 108 ms 11 ms 11 ms 10 ms 10 ms bb2-g1-3-0.skt2ca.sbcglobal.net [68.120.211.228]

4 12 ms 12 ms 12 ms 12 ms 12 ms 178 ms 204 ms 13 ms 48 ms 12 ms bb1-p10-2.crscca.sbcglobal.net [151.164.191.241]

5 13 ms 13 ms 13 ms 98 ms 13 ms 12 ms 13 ms 13 ms 14 ms 12 ms ex2-p9-0.pxpaca.sbcglobal.net [151.164.243.47]

6 13 ms 13 ms 13 ms 13 ms 13 ms 13 ms 13 ms 13 ms 13 ms 14 ms paix.pao01.mzima.net [198.32.176.38]

7 34 ms 27 ms 38 ms 28 ms 38 ms 29 ms 39 ms 31 ms 27 ms 33 ms pos4-0.cr01.lax02.mzima.net [64.235.224.81]

8 27 ms 27 ms 27 ms 26 ms 27 ms 27 ms 27 ms 27 ms 26 ms 26 ms ge1-1.ar01.lax02.mzima.net [64.235.224.214]

9 25 ms 26 ms 26 ms 25 ms 26 ms 25 ms 25 ms 25 ms 26 ms 25 ms 72-37-147-22.la.aim2game.com [72.37.147.22]

 

Ping statistics for 72-37-147-22.la.aim2game.com

Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)

Round Trip Times: Minimum = 25ms, Maximum = 26ms, Average = 25ms

 

Target Name: 72-37-147-22.la.aim2game.com

IP: 72.37.147.22

Date/Time: 2/17/2006 8:19:45 PM to 2/17/2006 8:20:07 PM

 

1 9 ms 9 ms 10 ms 13 ms 10 ms 10 ms 10 ms 10 ms 9 ms 9 ms [68.123.1.254]

2 9 ms 10 ms 10 ms 10 ms 10 ms 11 ms 10 ms 10 ms 11 ms 9 ms dist1-vlan50.skt2ca.sbcglobal.net [68.120.211.66]

3 10 ms 11 ms 10 ms 10 ms 11 ms 10 ms 10 ms 13 ms 10 ms 10 ms bb2-g1-3-0.skt2ca.sbcglobal.net [68.120.211.228]

4 12 ms 12 ms 12 ms 12 ms 12 ms 12 ms 12 ms 14 ms 40 ms 13 ms bb1-p10-2.crscca.sbcglobal.net [151.164.191.241]

5 13 ms 38 ms 87 ms 13 ms 13 ms 13 ms 14 ms 36 ms 13 ms 13 ms ex2-p9-0.pxpaca.sbcglobal.net [151.164.243.47]

6 13 ms 13 ms 13 ms 12 ms 14 ms 13 ms 13 ms 13 ms 14 ms 13 ms paix.pao01.mzima.net [198.32.176.38]

7 38 ms 29 ms 26 ms 32 ms 27 ms 33 ms 27 ms 34 ms 28 ms 36 ms pos4-0.cr01.lax02.mzima.net [64.235.224.81]

8 27 ms 29 ms 27 ms 27 ms 26 ms 26 ms 226 ms 44 ms 27 ms 26 ms ge1-1.ar01.lax02.mzima.net [64.235.224.214]

9 26 ms 26 ms 25 ms 25 ms 25 ms 25 ms 26 ms 25 ms 26 ms 25 ms 72-37-147-22.la.aim2game.com [72.37.147.22]

 

Ping statistics for 72-37-147-22.la.aim2game.com

Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)

Round Trip Times: Minimum = 25ms, Maximum = 26ms, Average = 25ms

 

after watch watching now for 5-10 mins i have about 4 routers that are spiking into the 100's and 200's. I am also getting 10% loaa on 3 or 4 routers on and off.

Edited by FORZ
Link to comment
Share on other sites

pretty bad today. if you guys can start recording demos each round, that'd be a big help. i've just been doing something like "record Dust1" and stopping it each round. if there's no rubberband, i just record over dust1. if i get one, "record dust2" for the next one. that way you don't have 50 bajillion demos to sort through to try and find the one rubberband ;)

 

again, thanks, and either post or email those demos.

Link to comment
Share on other sites

we need demos we need demos we need demos.

 

please put a post it note on your monitor. i'm trying to get in the habit of starting a new demo each and every round.

 

start round -> record rubber1

end round -> any rubberbands? no -> start round -> record rubber1

end round -> any rubberbands? yes -> start round -> record rubber2

 

you can help by doing the same. if i'm the only one with demos, the inevitable response is "it must be something with your computer or connection."

 

the more evidence i have, the easier and quicker we can fix it.

Link to comment
Share on other sites

both ptbx and csp have been removed for the day. lemme know if it improves the situation.

I was going to ask if you tried removing the csp yet. I'm seeing some of these same issues on #1(Recrud). And I'm wondering if it's being caused by the csp authentication.

Link to comment
Share on other sites

:(

 

removing csp and ptbx didn't solve the jitterbug. it did, however, prove the true worth of ptbx.

 

1. last night we had three blowouts in the couple hours we played. lol i completely forgot about the blowout rule until then. ptbx never lets that happen.

 

2. quote of the night from some pubber. "how come everyone keeps joining the winning team?" my reply "because we broke up with ptbx. she'd never let that happen." and she wouldn't.

 

a bit sidetracked, but ptbx FTW. the jitterbug (aka rubberband) is my nemesis. i am talking with a2g, and they're dedicated to fixing it for us. sit tight.

 

meanwhile, ptbx and csp are back on:

09:02:07 plugin_print

09:02:07 Loaded plugins:

---------------------

0:<TAB>"PTBx v1.7x1d3, Team Balancer. Copyright 2004-2005 XAD. (Original Team Balancing code, Copyright Ptahhotep.)"

1:<TAB>"CAL Server Plugin 1.1 - made by opi"

---------------------

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...