Choose resources for the kind of Left 4 Dead 2 sessions you host: consider the map and mode, active players, and any installed custom content. Start with the MaximusHost recommendation, then check resource use during a representative session.
Recommended resources
When creating a server, you can choose 1–8 GB RAM and 1–4 vCPU. We recommend starting with 2–4 GB RAM and 2–3 vCPU for a typical group. The creation page shows the available options and estimated cost before you continue. A demanding map or add-on may need more resources, so check usage during play.
For ordinary private sessions, begin near the recommendation rather than choosing the maximum without evidence. If your group relies on a custom map or a specific mode, test that combination before a scheduled event. A resource choice that worked on a stock map does not prove every installed map will behave the same way.
When testing, use the same map and mode your group plans to play and invite a representative number of players. That gives you a more useful comparison than checking a quiet server or changing resources based on a single brief slowdown.
RAM and CPU are not interchangeable
RAM supports the server process and its working data. CPU time handles active game and server work. If the server is slow during gameplay but memory is not under pressure, increasing RAM may not help. If the manager shows a repeated resource issue, compare it with console output and the map currently running before making a change.
Use Resources and Console/Logs during a real session, not only while the server is empty. Note the map, mode, when the issue occurred, and whether it affected everyone. Those details help narrow down the cause.
Why maps and modes matter
In L4D2 Tools, you can find installed maps, choose a default map and mode, or change levels during a session. Available modes include co-op, realism, versus, survival, and scavenge. Match the mode to the map; for example, survival maps usually need survival mode.
If a problem happens only on one map, check that the map is installed and detected, that the BSP name is entered without .bsp, and that the matching mode is selected. Do not treat a map-specific error as evidence that every server needs more resources.
Measure a representative session
Use a repeatable test:
- Choose a stock map and mode your group normally plays.
- Record RAM and CPU while the server is idle and during active play.
- Repeat with the custom map if one is part of the plan.
- Note console errors and whether all players see the same issue.
- Change one variable and repeat the same scenario.
This separates a resource pattern from a map, mode, connection, or setting issue. Avoid changing RAM, CPU, map, and server properties at once because you will not know which change affected the result.
When to change resources
If comparable sessions repeatedly show resource pressure, check the console for other errors and consider increasing one resource within the available range. Compare the next session under similar conditions. Reduce an allocation only after several representative sessions stay comfortably below it.
If only one player has a problem, check that player’s connection and game client. If everyone encounters an issue after a map change, return to the last working map and mode, then review the console. More RAM or CPU will not install a missing map or fix incompatible content.
Budget a session with credits
The creation page estimates costs from your selected resources and expected running time. Review Billing & Credits for how account charges work, and visit Left 4 Dead 2 hosting to see current server options.
Plan around the sessions your group will host, test custom maps before game night, and use actual resource readings to decide whether a change is warranted.
