SRCDS Steam group

Concerns with intermittent choke on net_graph (CS:S)
I run my server on windows server 2008 r2 with some sort of timer service and I get around 680fps. The server hardware is an old athlon 64 fx53 @ 2.4GHz and I have 2gb of ddr400 ram. I run mani, sourcemod, metamod, eventscripts all with no problems. I am on a verizon fios connection and I have something like 10 or 15mbps up bandwidth.

I run a surf cs:s server locally on the same LAN as me, so when I connect to it I have like 5-10 latency and everyone else will usually be like 40+.

Usually all is fine, but sometimes I start to notice low-ish choke (6-10), especially when other people or myself are using the voice chat or if there is a lot of stuff going on or right at round_start. It only lasts briefly and I usually see it as zero for most of the time.

I am wondering if this is anything that I should be worried about, and also if there is anything I can do to lower it?

I don't think there is anything in my server.cfg file aside from these few lines that may affect things:

sv_maxrate 30000
sv_minrate 15000
sv_maxcmdrate 100
sv_maxupdaterate 100
sv_minupdaterate 66
sv_mincmdrate 66

If anyone can offer any advice or explanation as to what may be causing this choke or how to possibly lower it I would appreciate it. I ask because some servers I play on seem to have pretty high choke most of the time (like 20-40+) and other servers don't have any choke at all ever.
That processor and RAM is aging, I'm not sure if that hardware will be sufficient for anything large on the Orangebox Engine. This is probably why.

Also the latency issue cannot be solved with hosting on a home connection. Even if it is FiOS, it's still a low priority residential connection.
Looking for a game server? Visit and pick one up as low as $2.50 / mo!
Peoples' latency is fine (and the server fps usually stays above 600), and the choke isn't really a serious problem, it is just something I notice and kind of bugs me Sad
So I suppose this is nothing to worry about? >_>
choke is commonly a connection problem, or a problem of client-side settings... server hardware usually has very little to do with it. (Linux Kernel HOWTO!)
Do not ask technical questions via PM!

Forum Jump:

Users browsing this thread: 1 Guest(s)