Optimize a server for 100+ players

Past a hundred concurrent players, default server limits and poorly written client scripts become the bottleneck. Optimization targets three areas: network, server CPU, and the database.

Cause / The problem

Tickrate drops and desync usually come from outdated artifacts, a non-OneSync server, client loops that run every frame (while true do without Wait), or unindexed SQL queries run for each player. The higher the slot count, the more these issues stack up.

Solution

1. Enable OneSync in server.cfg:

   set onesync on
   set onesync_population true

   OneSync handles entity synchronization natively beyond 32 players.
2. Update server artifacts (Linux or Windows) from the official Cfx.re site. A recent build fixes memory leaks and improves networking.
3. Adjust entity limits carefully: raise sv_enforceGameBuild only if a DLC requires it, otherwise the client loads unneeded assets.
4. Lighten client scripts. Spot loops without Wait, systematic Citizen.Wait(0) calls, and dozens of DrawMarker calls. Use the Resource Monitor to target the heaviest resources.
5. Optimize the database. Add indexes on the identifier and owner columns of players/vehicles tables, and switch to oxmysql (prepared statements + pooling) instead of legacy async MySQL drivers.
6. Monitor txAdmin. The Metrics tab shows tickrate, CPU and RAM in real time. A tickrate over 30 ms means a resource is hogging the main thread.

Also watch the network: set sv_maxClients 128 is only realistic if the machine has the matching CPU and bandwidth.