FiveM lag rarely has a single cause. The way to fix it is to measure instead of guess. Below is what each tool shows you and the typical causes, in order.
1. Measure first: resmon
Use resmon true in F8 to inspect client resource CPU time and memory. This is not a server CPU measurement. Compare resources during the affected scenario rather than treating one ms threshold as universal. If access is denied, consult the developer mode instructions in the Cfx.re documentation.
2. Read the hitch warnings
Correlate hitch warning messages with load at the same time; a warning alone does not identify the responsible script. Capture a sample with profiler record 500 in the server console and inspect CPU spikes and resources to narrow down the bottleneck.
3. The infinite loop trap
The while true do ... Wait(0) end pattern runs every frame. If the code does not truly need to run that often, raising the wait (for example Wait(500)) gives immediate relief. Many resources all running every frame will slow the server even on fast hardware.
4. Database latency
If player data is written to the database on every action, queries pile up and the whole server waits. Running the database on the same machine instead of a remote host lowers latency. Make sure frequently used tables are indexed and avoid writing rows you do not need.
5. Player count and OneSync
OneSync is used to raise the player limit. As players increase, so does the number of entities processed every frame, and that is where hardware starts to matter. The values below are starting points for a typical RP server.
| Server type | Recommended RAM |
|---|---|
| Test / development (1–32 players) | 4 GB |
| ESX or QBCore RP (32–64 players) | 8 GB |
| Large RP with OneSync (64–128 players, MLO maps) | 16 GB |
| City server (128+ players, heavy scripts) | 24 GB |
6. Texture loss and MLO maps
Buildings disappearing or textures failing to load is usually not about server power but about the size of the custom content you stream to clients. Many unoptimised MLO and vehicle files push players against their memory limit. Removing unused stream files is the fastest fix.
7. Is it the server or the player's PC?
Client FPS drops, network latency and server stalls are different problems. Resmon helps inspect the client; a profile captured in the server console helps inspect server work. Investigate client and connection issues for individual complaints, and server or shared network paths for simultaneous complaints. These symptoms alone are not a definitive diagnosis.
Ping depends on routes, congestion and player connections. Measure from player networks when selecting a Turkey location; location alone does not guarantee fixed latency.
8. Keep your artifact version current
Cfx.re regularly publishes new FXServer artifacts. Older builds can carry known performance issues and incompatibilities. Back up your server files and database before updating, and confirm yo