WEST: Rubberband / lag / trouble thread

[stutters]

if you're having any performance related problems with the west / immutable server, please post here.

 

if your post does not inlcude a screenshot with net_graph 3, a link to a demo, or ping plots, IT WILL BE DELETED.

 

screenshots:

enable your console (options -> advanced -> enabled developer console).

press ` (above tab key), type net_graph 3

press F5 during "lag"

screen shots save to your /cstrike/screenshot folder automatigically

(C:\Program Files\Steam\SteamApps\stutters\counter-strike source\cstrike\screenshots)

please post them directly into this thread.

 

demo:

please only have one round per demo. a 20 minute demo with 30 seconds of lag etc. is not cool.

enable your console (see above: screenshots)

to start a demo, in console type record lag1

to stop the demo, in console type stope

if you did not capture any lag that round, it might be easier to record over lag1 (record lag1 at the next round)

if you did capture lag, next round type record lag2

demos are automagically saved to your /cstrike directory

(C:\Program Files\Steam\SteamApps\stutters\counter-strike source\cstrike)

demo's can NOT be attched to the forum. either link to via ftp or email it to me: johnny.spam@gmail.com

 

pingplot:

http://www.pingplotter.com

trace to the server (72.37.147.22) and post a screen shot or text (edit -> copy as...)

[meherdmann]

I'm getting pings of over 500 right now to Immutable.

 

Tracing route to 72-37-147-22.la.aim2game.com [72.37.147.22]

over a maximum of 30 hops:

 

1 1 ms <1 ms <1 ms 72-37-147-22.la.aim2game.com [72.37.147.22]

2 11 ms 8 ms 7 ms 10.16.128.1

3 13 ms 6 ms 9 ms 68.9.13.33

4 24 ms 36 ms 29 ms provdsrj02-so030.rd.ri.cox.net [68.9.14.29]

5 28 ms 29 ms 25 ms provbbrj01-ge020.rd.ri.cox.net [68.1.0.48]

6 33 ms 33 ms 33 ms NYRKBBRJ01-so000.R2.ny.cox.net [68.1.0.51]

7 55 ms 36 ms 48 ms 68.1.0.253

8 48 ms 41 ms 36 ms 68.1.0.250

9 39 ms 39 ms 40 ms mrfdbbrj02-ge030.rd.dc.cox.net [68.1.1.3]

10 41 ms 48 ms 39 ms ashbbrj02-so000.r2.as.cox.net [68.1.1.232]

11 54 ms 53 ms 41 ms ashbbbrj01-ae0.0.r2.as.cox.net [68.1.0.220]

12 43 ms 48 ms 53 ms eqix-peer.iad01.mzima.net [206.223.115.62]

13 597 ms 597 ms 594 ms pos5-0.cr01.lax02.mzima.net [64.235.224.77]

14 585 ms 583 ms 586 ms ge1-1.ar01.lax02.mzima.net [64.235.224.214]

15 589 ms 588 ms 583 ms 72-37-147-22.la.aim2game.com [72.37.147.22]

[Laz.e.rus]

Thank you.

Good catch and plot. Thatll definitely help.

[FORZ]

Well I dont have demos or anything. But I think the reason for the lagg is mani or some other app on the sever is eatting up the cpu I dont think it has much to do with connection prolblems. I think mind u I have no proof, but I think when the sever fills with number of admins and a number of people using damage system combind with the stats system It causes mani too us too much of the cpu witch causes the rubber-banding. Some Things they could do to test this is force cs:s ded server to high and mani to low prossore priority. Mind u I have no clue what kinda systems a2g is running and what kinda monitoring tools they use to monitor cpu useage history. It doesnt appear to happen without mani. So I think its either time to test a new plugin or get rid of some of mani's features.

 

On another note ask how may severs they are running off one box if its more then one It will never stop rubber banding, cause alot of servers companys have found that u can not run more then one server on any kinda box no matter the specs. I dont have the link but I know 2 server company have publicly stopped selling source sever because they cant run more then one source server off top of the line server platforms and it was too cost ineffective to run one source sever when they could sell the same box 3 times with other games.

Edited July 22, 2006 by FORZ

[stutters]

I think when the sever fills with number of admins and a number of people using damage system combind with the stats system It causes mani too us too much of the cpu .... get rid of some of mani's features.

disabled a few modules via leadadmin. new settings below:

 

mani_stats_most_destructive 0

mani_show_victim_stats 0

mani_voting 0

mani_show_death_beams 0

we were running pretty barebones w/ mani for over a week before we tried the new batch of test servers. even still we were over stressing the boxes.

[Elocin]

This is a screeny from today or yesterday cant remember (faulty memory)http://www.forztek.com/Downloads/Strats/de_aztec0002.jpg

Edited July 25, 2006 by Elocin

[Laz.e.rus]

np. Im posting this for you in the GC General Source sticky that fatty made for this kind of info.