[daveyboye]

I wanted to create a thread to where server owners can compare their server rates and performance cvars. That way people can tinker with what works best. Please include your game server type, what host you are with, what operating system you are on, and your maxplayers.

I operate [____Skul`Shock____] for HL2DM
Nuclear Fallout Servers with Higher CPU Priority and Hyperaccelerating
Windows Server 2008
Maxplayers - 16

//////////////////////////////////// Rates//////////////////////////////////////
sv_lan 0
sv_unlag 1
sv_maxunlag .5
sv_minrate 100000
sv_maxrate 0
sv_minupdaterate 33
sv_maxupdaterate 66
sv_mincmdrate 33
sv_maxcmdrate 66
sv_client_cmdrate_difference 1
sv_client_predict 1
sv_client_interpolate 1
sv_client_min_interp_ratio -1
sv_client_max_interp_ratio -1
sv_max_queries_sec 10
sv_max_queries_sec_global 60
sv_parallel_packentities 0
sv_parallel_sendsnapshot 0
net_splitpacket_maxrate 100000
fps_max 0

[Snaggle]

This could be handy: http://www.reece-eu.net/drekrates.php

Though I'm not sure if things have changed or not, that link may not be accurate. And it seems to be for home servers?

[daveyboye]

They have shown to make a dramatic difference for me. It neutralizes everything. It's better to narrow your minimum and maximum cvars so server is putting out almost the same information to all players. It really aids in smooth gameplay and also better hit registry. Also, minimizing ques also helps prevent against game server specific DDOS and flooding of the server.

[nikooo777]

Originally Posted by matr1x Believe me, friend. Half, if not most, of what you just said is pure mockery.

can somebody please just tempban this troll? I think he's trolled enough today already.


For any new member or non acknowledged member that is trying to figure out the rates:

It's very important to balance them in your gameserver because it has a big influence in the CPU usage and the bandwidth usage other than ingame performances. You will notice those things when you start having a big and populated server, when the server is not any bigger than 24 players or so, unless you have a single-core slow cpu, you shouldn't notice big differences.

Hitreg is highly related to the rates too because it relies on how many updates the gameserver receives and sends from/to the client. The more updates you have, the better it is. (requires more bandwidth and CPU)


source: Years of experience with srcds

[daveyboye]

Originally Posted by nikooo777 It's very important to balance them in your gameserver because it has a big influence in the CPU usage and the bandwidth usage other than ingame performances. You will notice those things when you start having a big and populated server, when the server is not any bigger than 24 players or so, unless you have a single-core slow cpu, you shouldn't notice big differences. Hitreg is highly related to the rates too because it relies on how many updates the gameserver receives and sends from/to the client. The more updates you have, the better it is. (requires more bandwidth and CPU) source: Years of experience with srcds

Agreed, I've had to change my rates many times when switching providers. You have to learn your providers shared hosting and see how much resources your server is taking up and how many other resources are being taken up by other servers. I sure do miss the day I ran my own dedicated box and my servers were the only ones on there. We maxed out everything when it came to rates . I'm hoping this thread will become a place people can share their rates/performance cvars with what kind of environment they are in. Just trying to help out other server owners. I've been operating Skul`Shock since 2006 and wanted to give back to the larger community.

[cool_myll]

// Min bandwidth rate allowed on server, 0 == unlimited sv_minrate 30000 // Max bandwidth rate allowed on server, 0 == unlimited sv_maxrate 30000 // Minimum updates per second that the server will allow sv_minupdaterate 66 // Maximum updates per second that the server will allow sv_maxupdaterate 66 sv_maxcmdrate 66

Arent those the max settings if your server can handle it?

[daveyboye]

Originally Posted by cool_myll Arent those the max settings if your server can handle it?

No, you can go higher with cmdrate and updaterate if your server has the tickrate hack. 30,000 is the maximum rate for sv_maxrate.

[nikooo777]

alright here we go

// bandwidth rates/settings sv_minrate 40000 sv_maxrate 0 sv_minupdaterate 66 sv_mincmdrate 66 sv_maxupdaterate 67 sv_maxcmdrate 67 net_maxcleartime .01 net_splitpacket_maxrate 100000

fore newbies: Don't copy paste, they will likely not work for you, i am running those settings on a quadcore 8 threaded 3.3GHz and a Gbit network...

[daveyboye]

Originally Posted by nikooo777 alright here we go fore newbies: Don't copy paste, they will likely not work for you, i am running those settings on a quadcore 8 threaded 3.3GHz and a Gbit network...

What's the net_maxcleartime .01 cvar? Never heard of that one. Also, what game you running. I believe the orangebox engine is capped at 30,000 rate.

[Bacardi]

Originally Posted by daveyboye ... Also, what game you running. I believe the orangebox engine is capped at 30,000 rate.

Nope, it isn't.
It's default rate value for players now, when they play game first time, if they don't know how use console or change rate settings.

"rate" = "50000" ( def. "30000" )
 archive
 - Max bytes/sec the host can receive data

Before OB update, default rate value was 10000, really LOW and cause choke and high pings etc. etc. when server run tickrate more than 33.
Those settings have stayed from HL2 game.

Sometimes even 30,000 is not enough in TF2 game, there happen lot of action when all players attack in same time.
----------------------

Spoiler

Spoiler

Spoiler

I have thinking, those who host big server (30 players or more) and can't keep that updaterate staying to 66,
so its start drop close to 30 and back 60 etc. etc. up and down.
Why not try cap update rate to 20 or 30 ?
What I have tested (with bots), it work very well. And will take less bandwidth.

Spoiler

sv_maxrate 0; sv_minrate 30000
sv_maxupdaterate 20; sv_minupdaterate 20
sv_maxcmdrate 66; sv_mincmdrate 30
sv_client_cmdrate_difference 100
net_splitpacket_maxrate 30000