Posts: 18
Threads: 4
Joined: Sep 2007
Reputation:
0
ok how do you find out player slots to bandwith?
Posts: 5,178
Threads: 65
Joined: Mar 2005
Reputation:
22
well a 33 tick server will use around 5KB/s per player (that's 40kbps)
66 uses around 10KB/s per player (80kbps)
100 around 15KB/s per player (120kbps)
note that the more players you have, the bandwidth increases exponentially, for example a busy 66 tick server (like 24 players) can easily make 20KB/s per player (160kbps)
Posts: 18
Threads: 4
Joined: Sep 2007
Reputation:
0
Ok thank you that is some good info, now how do i find a good way to check how many slots the hardware can take?
Posts: 18
Threads: 4
Joined: Sep 2007
Reputation:
0
what i want to know is the how did you come up with 100-150 players slots? that is what i want to know players to hardware?
Posts: 5,178
Threads: 65
Joined: Mar 2005
Reputation:
22
It's just a quick estimate, I know from experience what certain processors can run on average. I know a C2D E6600 can run 100slots for example, P4 3.0GHz can get 60, etc etc.
I think I misread your specs, cause you have 2x opteron so that's 4 cores total, am I right?
That case you should be able to get 150 slots I think.
Since every machine is different you can't tell exact numbers.
Posts: 18
Threads: 4
Joined: Sep 2007
Reputation:
0
yes you are right it does have 4 cores. so 150 slots should run with no problem, now because it has fir cores do i assign a 32 man server to one of the cores in fire daemon or just let windows do that?
Posts: 1,587
Threads: 15
Joined: Jun 2005
Reputation:
0
Well mainly i think windows doesn't really worry about setting a process to a different core unless the core if at 100%. but with game servers thats wayy too late. Setting affinity is more like a proactive approach. Windows doesn't know how much resources the srcds.exe process is going to need until it needs it. Then again thats to late.
Posts: 18
Threads: 4
Joined: Sep 2007
Reputation:
0
ok cool thanks for all the great info