Slot planning on a game server: how much resource for how many players?

The question "how many slots" is misleading, because a slot is not a capacity but an upper bound. Opening 128 slots does not mean the server can carry 128 players; it only means the 129th person cannot get in.

The three things that decide

Your resource requirement comes not from the slot count but from these three:

1. Concurrent active players — the number actually connected at peak hour
2. Simulation load per player — this varies tenfold between games
3. Fixed load — the resource/plugin list, the world, the database

The right approach is to set the slot count 20-30% above the realistic peak. Opening it far too high is an invitation to a crash when the server fills up.

Per-player load by game

The same player count needs entirely different resources depending on the game:

The "fixed load" in the table is independent of the slot count and on most servers is the larger part of the total requirement. The difference between a 16-slot and a 64-slot FiveM server is smaller than you would think — because both load the same 100+ resources.

The two ends of the table therefore call for entirely different decisions. In Minecraft the deciding factors are view-distance and the plugin list rather than the player count. In Rust what really inflates the fixed load is worldsize and the structures accumulated between wipes — the same player count needs a different plan on a different map size.

A worked example

A 64-slot FiveM server with 45 active players at peak hour:

Linux baseline             1.0 GB
Resource list + stream     6.0 GB
45 players × 50 MB         2.3 GB
MariaDB                    2.0 GB
---------------------------------
Total                     11.3 GB  ->  16 GB plan

An 8 GB plan sits at the limit during peak hours; 16 GB leaves comfortable headroom. To see the difference as a monthly total, use the server configurator, where each resource is picked individually.

When is raising the slot count not enough?

Raising the slot count and adding RAM works up to a point on most games, and then hits the CPU wall. FiveM, Minecraft, Rust and a single Metin2 channel do their main work on one thread; once that core is full, adding slots only means more players experiencing the same latency.

The symptom is this: memory is plentiful, top shows a single core pinned at 100%, and players report stuttering. At that point the answer is upgrading the processor family or splitting the load — both are resource choices you make on the virtual server plans. Details: how many vCPUs and how much RAM?

A practical checklist

When making the slot decision, in order:

1. How many people are actually connected at peak hour? (a measurement, not an assumption)
2. How large is your fixed load? (resource list, mod pack, world size)
3. Take the per-player load from the table, multiply, add up
4. Move to the plan 30% above the result — leave headroom for the peak
5. Set the slot limit 20-30% above the realistic peak

Next step

We have put the RAM, vCPU and storage guidance by player range for every game, together with prices, on one page: game server plans.

If you are adding voice chat for the community, the slot calculation comes up a second time: whether managed TeamSpeak hosting or your own install on the same machine works out cheaper is set out with monthly amounts in the cost comparison per slot.