How to Keep Your Counter-Strike 2 Server Running Smoothly

This guide explains what uses your Counter-Strike 2 server’s resources, and the simple steps that keep it running smoothly.

---

​

Check what your server uses

Before you change anything, look at the numbers:

• Console: the right column shows CPU, Memory, Disk and Network right now.
• Statistics: CPU and memory over the last hour, day, week or month. See how to view server statistics.
• Alerts: get an email when the disk is almost full or memory hits its limit. See how to set up server alerts.

Lag that happens to everyone at the same moment usually comes from the server. Lag for one player only is usually their own connection.

---

​

CPU and RAM

If CPU is high only during busy matches, you’re close to your plan’s limit. If memory keeps climbing over days, a plugin may be leaking memory: restart the server regularly and check your plugins. When an empty server has nobody on it, CS2 puts it into a low-CPU sleep mode (hibernation). It wakes up when a player joins.

---

​

Bots cost CPU

Players’ game clients do most of their own work, but every bot thinks, moves and aims on the server itself. Each bot adds CPU load.

• Set Bots to 0 in Server settings when you don’t need them.
• For practice, add bots only when needed with bot_add_ct or bot_add_t, and remove them with bot_kick.
• Deathmatch with many bots is one of the heaviest setups.

See server configuration.

---

​

Keep your plugins tidy

• Only install what you use. Each plugin adds work, especially ones that run every tick or on every shot.
• Remove old plugins you no longer use, instead of leaving them loaded.
• Find a slow plugin by turning plugins off one at a time on the Plugins page, then restarting and watching CPU.
• Keep plugins updated. After a big CS2 update, check each plugin’s page for a new release.
• Give database plugins a real database. Use the host from the Databases page. See frameworks and plugins.

---

​

Updates and file checks

Your server checks Steam for a CS2 update each time it starts. Players must have the same CS2 version as the server to join, so keep updates on. After a CS2 update, open Frameworks and click Repair gameinfo.gi if your plugins stopped loading. See troubleshooting.

---

​

Tickrate and sub-tick

CS2 uses sub-tick updates: the server records the exact moment you shoot or move, between ticks. That’s why there is no tickrate setting to change in Server settings, and why “128 tick” in a server name means nothing in CS2. If hits feel wrong for one player, check that player’s ping and packet loss first. If they feel wrong for everyone, check the server’s CPU on the Statistics page.

---

​

Keep the disk healthy

• Delete old GOTV demos and logs you don’t need. See popular setups.
• Use automatic backups with a sensible number to keep.
• A nearly full disk can stop updates and saves. Turn on the Disk almost full alert.

---

​

Related articles

---

---