Troubleshoot CS2 Server Performance Issues
Step-by-step guide to diagnosing CS2 server performance problems — high server simulation time, stutters, and crashes. Covers plugin isolation, identifying the scope of the issue, reading server logs, and when to contact support.
The #1 Cause: Plugins
The vast majority of CS2 server performance issues are caused by plugins — specifically CounterStrikeSharp or MetaMod plugins that have bugs, memory leaks, or do too much work on each tick.
Start here: Disable all plugins and test the server with vanilla CS2. If performance is fine without plugins, re-enable them one at a time to identify the culprit.
Step 1: Check the Scope
Is the issue affecting all players or just some?
- All players lagging → Server-side performance issue (CPU, memory, plugin, network)
- Only specific players lagging → Client-side issue for those players — see CS2 High Ping and Packet Loss
Step 2: Check Server Metrics In-Game
Open the console (`) and run:
net_graph 1
Watch the sv: value:
| sv value | Interpretation |
|---|---|
< 4ms |
Server is healthy — performance issue is elsewhere |
4–8ms |
Elevated — server is under load; check CPU usage in panel |
> 8ms |
Server is bottlenecked — plugins, high player count, or hardware limit |
Also check choke: — a non-zero choke means the server can't keep up with sending updates at the configured tickrate.
Step 3: Disable Plugins
- In your AMP or WISP panel, navigate to your CS2 server
- Open File Manager and rename or remove plugin folders in
addons/counterstrikesharp/plugins/— start with CSS plugins, then disable MetaMod if needed - Restart the server and test
If performance improves, your issue is plugin-related. Re-enable plugins one at a time, rebooting between each, until the problem returns. The last plugin you enabled is the culprit.
Step 4: Check Server Logs
In the panel's File Manager, look in addons/counterstrikesharp/logs/ for error messages from CounterStrikeSharp and its plugins. Common patterns:
| Log Pattern | Likely Cause |
|---|---|
NullReferenceException in a plugin |
Plugin bug — update or remove it |
OutOfMemoryException |
Memory leak — restart server, remove plugin |
Repeated Exception from same plugin every round |
Plugin incompatibility with current CS2 build |
[MetaMod] Failed to load |
MetaMod/plugin version mismatch |
Step 5: Check Panel Resources
In your AMP or WISP panel, check server resource usage:
- CPU consistently > 80% → Server is overloaded. Options: fewer players, fewer plugins, or a higher-tier plan.
- Memory consistently > 80% → Memory leak or too many plugins. Restart on a schedule (e.g. nightly) and investigate.
Step 6: Server Restarts
CS2 servers can accumulate memory fragmentation over time. Scheduling a daily restart is standard practice:
- In your panel, look for a Scheduled Tasks or Restart Schedule setting
- Set a nightly restart at a low-traffic time (e.g. 4 AM in your server's timezone)
- This clears memory leaks and applies any pending game updates
When to Contact Support
If you've ruled out plugins and client-side causes and performance is still consistently poor, reach out in our Discord at discord.dustbowl.games. Bring:
- Your server region and IP
- The time range of the issue
- A
net_graph 1screenshot showingsv:andchoke:values - Whether disabling plugins made a difference
- CPU/memory usage graphs from your panel if available