FiveM Upvotes
Hosting & infrastructure

resmon

Also called resource monitor

The in-client profiler that shows how much CPU time each resource consumes per frame.

resmon 1 in the F8 console opens the resource monitor: a live table of every running resource and the milliseconds it costs per tick, client-side. resmon 2 adds the server side.

The numbers to care about are the per-resource times under load, not at idle. A resource that costs 0.01 ms with one player and 4 ms with sixty is the one hurting you, and it will not show up on an empty test server. Anything consistently above about 0.5 ms client-side deserves a look; anything above 2 ms deserves a rewrite or a replacement.

The usual culprits are loops without waits, per-frame drawing that should be distance-gated, and NUI pages left running when hidden. Fixing two bad resources routinely does more for perceived server quality than doubling the hardware.

Performance is a retention problem rather than only a technical one: players do not file bug reports about stutter, they leave.

Related terms

ResourceA self-contained folder of scripts, assets and a manifest that the server loads to add functionality.OneSyncThe Cfx.re server-side synchronisation model that lifts FiveM past the original 32-player ceiling.PingRound-trip latency between a player and the server, and the main reason a player picks one region over another.

Trying to get your server seen?

The live leaderboard shows what the numbers look like at the top of the list, and the upvote calculator turns a target server into a campaign size. The full glossary is here.