Constant 1% choke with spikes on each round start (CS:GO / S

[HowIChrgeLazer]

Hey everyone,

I was wondering if somebody could help me confirm my suspicions. I have a VDS in LA that used to run Server 2008 R2. I did an upgrade to my package which moved me to a new box. Before I checked the performance of the move, I decided to start from scratch on Server 2012. SteamCMD and SRCDS work and launch with no issues.

However, on servers that were setup exactly the same (with the same plugins for sourcemod @ 128 tick) I'm getting a constant 1% choke during rounds, plus spikes. Which didn't happen previously.

So it could be one of two things. The box I was moved to (which I doubt) or Server 2012. Anybody have experience with these issues on Server 2012?

[soja]

I highly doubt choke would be effected by a server move.

What is your sv_maxrate?

Slot count?

Have you experimented with net_splitpacket_maxrate?

[HowIChrgeLazer]

Slot count is default 20.

Right now sv_maxrate is 0, but it was choking with just a friend and I in the server using the rates we used on the old setup that had no choke on a full game.

I have my rate set on my client side, thought it was just me and had him join. He was getting the same choke as well.

I have not attempted to change net_splitpacket_maxrate. Any recommendations for the NFO network on that cvar?

[Spray]

We actually don't specify net_splitpacket_maxrate by default on our CS:GO installations. Do you get this same type of choke on the server running at 100 tick?

[kraze]

Setting net_splitpacket_maxrate to 128000 would be good or you can do something lower such as 100K.

Also be sure you're forcing a high minrate, setting this to something like 100K and leaving the maxrate uncapped like you have it now would be good.

[soja]

Choke happens when the server tries to send more information than the client rate settings allow.

What did you have rate set to on your client when you joined? Is it a default map?

[HowIChrgeLazer]

Appreciate the input so far on this,

Tried some of the settings given here. Here's an update:

Map: de_dust2
Rate: 100,000 (sv_minrate was bumped up to this as well from 70k, my client was at 80k)
net_splitpacket_maxrate: 128000

Choke spike on round starts have gone from 50% down to 5%. Choke sits at 0% now aside from firefights where it still comes up to 1%.

EDIT: Looks like rate 110k eliminates all but a blip of choke during testing with bots. (aside from the short 4% spike on round restarts)

[soja]

Choke between 0-5% is acceptable, but should be avoidable with your current settings. What is your server IP so I can check it out for myself?

[Edge100x]

We default to a high sv_minrate such as 128000 here. I recommend also setting this on your server. As soja said, choke occurs when the server believes that it would exceed the negotiated rate, so it holds back updates to a client.

We talk a bit more about choke here: http://www.nfoservers.com/forums/viewto ... =25&t=3930

[HowIChrgeLazer]

Choke between 0-5% is acceptable, but should be avoidable with your current settings. What is your server IP so I can check it out for myself?

So round loads are choking to 5%, but I don't view that as an issue as it's moving data to re-position models and respawn players. Everything else is at 0% during play now.

de.ragecagegaming.com

We default to a high sv_minrate such as 128000 here. I recommend also setting this on your server. As soja said, choke occurs when the server believes that it would exceed the negotiated rate, so it holds back updates to a client.

We talk a bit more about choke here: http://www.nfoservers.com/forums/viewto ... =25&t=3930

Had a full server using sv_minrate 128000 last night. Friends and I aren't getting choke during rounds. I did see one or two people lagging, but I'm chalking that up to the fact they were either downloading or they couldn't handle the 128 tick updates.

Thanks for the recommendation on those cvars guys, helped me get up to speed a lot quicker than having to check and change a bunch.