Info

How data is collected

FiveM has a built-in profiler that works at the C++ runtime level. You do not need to touch any script. When you run profiler record 300, FiveM's Citizen Lua scheduler wraps every thread tick in every resource with precise timing automatically.

The runtime tracks which resource owns each Lua coroutine, so it records execution time for all of them including escrowed resources. The resource name is never encrypted, only the code inside it, which is why you see entries like Escrowed (qbx_core).

When recording stops, run profiler saveJSON myprofile. Download that file from your server and upload it here.

Server ticks and the 50ms budget

A FiveM server runs at 20 ticks per second, one tick every 50ms. Within each tick, every resource's threads, event handlers, and commands run one after another.

The profiler groups events into ticks by looking for gaps over 15ms between consecutive events. That gap is the server sitting idle waiting for the next tick cycle. Everything within a gap is counted as one tick.

The script time per tick in the results is the total Lua execution time across all resources in a single tick. 5ms per tick is fine. 40ms per tick leaves almost no room for networking and entity sync, which is when players start feeling lag.

Heavy ticks

A tick is marked as heavy when total script execution goes over 25ms. That is half the 50ms budget. Once scripts are using more than half the budget, there is very little left for everything else the server needs to do.

The timeline chart shows every tick as a bar. Green is fine, yellow is getting close, red is a heavy tick. Hover over any bar to see what was running during that tick.

Top 20 Worst Scripts