Drek's HLDS / SRCDS rate calculator
This handy little chappy will calculate the recommended number of slots your HLDS or SRCDS server can run with rates, as recommended by Drek.
All calculations are directly from Drek's guidelines "setting rates for small home servers" (formerly "running a lag free server"), but since nobody can be bothered to read his highly useful and well structured advice, I have built this.
This script should work in IE/Opera/Firefox now. Thanks to pizzahut for help on getting it to work in Firefox.
20/Nov/2016: Increased GoldSrc maximum rate to 100,000 (SteamPipe) and added Sven Co-op dedicated server.
Not got a clue what to enter? Here's some help.
Game server engine
Select the game engine your servers will be running.
HLDS (GoldSrc) - this includes games such as:
- Half-Life Deathmatch
- Counter-Strike 1.6
- Counter-Strike: Condition Zero
- Team Fortress Classic
- Day of Defeat
- Deathmatch Classic
- Natural Selection
- Sven Co-op (earlier than version 5.0)
- Digital Paintball
- Science and Industry
- Any other mod based on the Half-Life engine
- SvenDS (GoldSrc modified) - This is for the Steam release of Sven Co-op 5.0 or later.
SRCDS (Source) - this includes games such as:
- Half-Life 2 Deathmatch
- Counter-Strike: Source
- Team Fortress 2
- Day of Defeat: Source
- Left 4 Dead
- Fortress Forever
- Obsidian Conflict
- Any other mod based on the Source (Half-Life 2) engine
Throughput (wrongly aka bandwidth)
Simply the lowest amount of throughput you have available to the Internet. If your downstream speed is 4 megabits, and your upstream speed is 512 kilobits, enter 512.
If you honestly have no idea, try the speed test. Do 2 or 3 tests on the recommended testing server to get an accurate result, then take the lowest figure out of downstream/upstream and enter it in the box.
5% of the value you give us will be taken off mainly to leave a gap that may be required for other protocols.
Finally, I call this throughput rather than bandwidth because bandwidth is a term used in radio frequencies. As computer scientists we should be using the correct term throughput to determine the amount of data we can put through a logical link within a certain time lapse.
We now need to know details about the server computer.
- MHz CPU: How fast the server processor is in megahurtz (MHz). Do not multiply this by the number of processors/cores/threads your CPU has. 1 GHz = 1000 MHz.
- Threads: The number of executable threads your server has. If your server has 2 physical processors with 4 cores on each, enter 8. Double this figure if your processor has hyper-threading enabled on an operating system supporting it.
- Primary memory: The amount of available primary memory (RAM) the server has. Real memory only, do not include virtual memory. Decimal points allowed (i.e. 1.5 GiB).
Once you enter your server processor speed, number of processors/cores, and total primary memory, the script will recommend how many slots it can handle.
Either take the recommended slots and type it in the player(s) including reserved slots box, or type in your own figure.
If you are recommended more than 32 slots, don't worry -- it isn't broken. This means you can run multiple servers up to the player count shown. For example if you are told 50 players, you could run 2 servers at 25 players each, or you could run 3 servers at 20/20/10 players.
Ensure you enter the total slots across ALL servers you intend to run on the machine. If you will be running 2 game servers with 20 slots each, enter 40. If you were to put in just 20, the rates advised will be for just 1 of your game servers.
Once you've filled in the throughput and players, you can calculate the rates recommended for your server configuration file. Simply copy and paste the results in to your server.cfg file.
If you would prefer to have an application for Windows that does this, see my original creation of this tool.
Page last updated Sunday, 20th November 2016 at 4:01 PM, executed in 0.011 seconds using 9 queries. It has been viewed 3,366,693 time(s).
Design and content © copyright Adam Reece 2003-2012. All rights reserved.
Please send any problems you encounter on this website to the manager Adam Reece, thank you.