Performance Optimization

BeamMP servers are lightweight by nature, but heavy mod loads and poor setup can cause lag, slow join times, and disconnections. These tips help you get the most out of your Vyper Hosting server.

Limit Cars Per Player

The single biggest performance factor. Each vehicle syncs physics data to every connected player, so players × cars multiplies bandwidth and CPU usage fast.

Recommended: 1–3 cars per player for general servers.
For race events needing multiple cars per player, reduce max players to compensate.
Set in the Cars field of the Startup tab.

Choose a Lighter Map

Some maps are far more demanding than others.

Lighter (high player counts):

gridmap_v2 - flat, minimal assets
smallgrid - tiny, very fast
small_island - compact open world

Heavier (smaller groups):

west_coast_usa - large and detailed
italy - large, many assets

For public servers, we recommend starting with a lighter map.

Keep Your Mod Count Sensible

Every mod in Resources/Client/ downloads to every joining player.

Remove mods you’re not actively using.
Avoid duplicate vehicle packs that cover the same cars.
Use the Mods tab to manage installed mods, it makes removal easy.
Test new mods one at a time to catch conflicts early.

Scale Cars with Player Count

Players online	Recommended max cars/player
1–5	3
6–10	2
11–20	1
20+	1 (enforce via CE vehicle restrictor extension)

Restart Regularly

Long-running servers can accumulate memory usage from abandoned vehicle data and plugin state. A weekly restart keeps things clean. Do it from the Console tab when player count is low.

Keep the Server Updated

New BeamMP versions often include performance fixes. See Updating Your Server.