Skip to main content

Original research

FiveM resource CPU cost, measured across 674 real servers

What this is

191,575 individual resource timings collected from 674 distinct FiveM servers between 2026-03-06 and 2026-10-05, covering 41,950 distinct resource names. The most widely deployed resource is tick (monitor) on 656 of 674 servers. The single most expensive tick ever recorded is 1268.1 ms from event:QBCore:Server:TriggerCallback (qb-core). Free to use under CC BY 4.0, with a CSV download below.

Read this before using the numbers

  • The sample is self-selected. These profiles came from people who chose to run a profiler, and most people do that because something is already wrong. Absolute costs here almost certainly skew worse than a random sample of FiveM servers would. Use the data to compare resources against each other, not to judge whether your own server is normal.
  • A resource is not a verdict. A high figure next to a resource name usually means a server is using it heavily or misconfiguring it, not that the resource is badly written. The most widespread resources naturally accumulate the most extreme outliers.
  • Framework counts are name matches. We count servers having a resource whose name contains, say, es_extended. That is a proxy for framework use, not a declared dependency.
  • Only resources seen on 10 or more servers are listed. Of 41,950 distinct names, the large majority appear on a single server — bespoke scripts and renamed copies. Publishing those would be noise.

Highest single ticks ever recorded

The worst one-off spike observed for each resource, among those appearing on 10 or more servers. A spike above roughly 50 ms is a visible hitch for players, since the server tick budget is about 50 ms.

FiveM resources by highest single recorded tick
ResourceWorst tickAvg per tickServers
event:QBCore:Server:TriggerCallback (qb-core)1268.1 ms2.379 ms66
tick (oxmysql)1023.9 ms0.093 ms605
tick (ox_doorlock)932.9 ms0.586 ms96
tick (dnc_police)759.1 ms16.610 ms14
event:__ox_cb_jg-advancedgarages:server:nearby-players (jg-advancedgarages)659.0 ms13.575 ms86
event:cocottMonsters:getPlayerData (cocott-monsters)634.8 ms88.209 ms12
event:esx:triggerServerCallback (es_extended)571.5 ms1.716 ms140
event:wasabi_ambulance:setDeathStatus (wasabi_ambulance)529.1 ms6.532 ms73
event wasabi_ambulance:setDeathStatus [@blueberry/shared_fg-obfuscated.lua[1..1]]525.1 ms11.180 ms34
tick (ns_sync)500.2 ms2.823 ms16
event QBCore:Server:TriggerCallback [@blueberry/shared_fg-obfuscated.lua[1..1]]484.0 ms2.525 ms42
tick (blips_creator)392.4 ms0.117 ms45

Highest sustained cost per tick

Mean per-tick cost, among resources on 25 or more servers. Unlike the table above, this is the cost a resource imposes continuously rather than in occasional spikes — it is what quietly lowers your baseline frame time.

FiveM resources by mean per-tick CPU cost
ResourceAvg per tickWorst tickServers
tick (ox_stashdurability)31.124 ms212.3 ms43
event __ox_cb_jg-advancedgarages:server:nearby-players [@blueberry/shared_fg-obfuscated.lua[1..1]]15.773 ms232.9 ms33
event:__ox_cb_jg-advancedgarages:server:nearby-players (jg-advancedgarages)13.575 ms659.0 ms86
event wasabi_ambulance:setDeathStatus [@blueberry/shared_fg-obfuscated.lua[1..1]]11.180 ms525.1 ms34
event chat:init [@chat/sv_chat.lua[264..281]]10.771 ms29.2 ms27
event:chat:init (chat)10.058 ms38.7 ms56
event hospital:server:resetHungerThirst [@blueberry/shared_fg-obfuscated.lua[1..1]]9.428 ms169.6 ms25
event:hospital:server:resetHungerThirst (wasabi_ambulance)8.814 ms207.0 ms30
tick (okokReports)8.156 ms137.5 ms38
event __ox_cb_jg-advancedgarages:server:nearby-players [?[474..710]]7.483 ms70.4 ms26
event:__ox_cb_qbx_core (qbx_core)7.108 ms22.2 ms25
event:wasabi_ambulance:setDeathStatus (wasabi_ambulance)6.532 ms529.1 ms73

Framework and library footprint

How many of the 674 profiled servers carry a resource matching each name.

605

of 674 servers

oxmysql

572

of 674 servers

pma-voice

504

of 674 servers

ox_lib

462

of 674 servers

ox_target

390

of 674 servers

ox_inventory

215

of 674 servers

ESX (es_extended)

112

of 674 servers

Qbox (qbx_core)

89

of 674 servers

QBCore (qb-core)

Most widely deployed resources

Top 100 resources by number of distinct servers running them. The full filtered table is in the CSV export.

FiveM resources by number of servers running them
#ResourceServersAvg per tickWorst tick
1tick (monitor)6560.073 ms224.0 ms
2thread @monitor/resource/sv_logger.lua[31..54]6430.041 ms75.4 ms
3thread @monitor/resource/sv_playerlist.lua[112..134]6330.183 ms43.4 ms
4tick (oxmysql)6050.093 ms1023.9 ms
5tick (pma-voice)5720.023 ms67.7 ms
6tick (ox_target)4610.052 ms14.2 ms
7tick (yarn)4560.028 ms59.2 ms
8event:ox_lib:validateCallback (ox_lib)4240.116 ms187.6 ms
9tick (screenshot-basic)4200.022 ms131.5 ms
10thread @ox_target/server/main.lua[25..48]3570.031 ms7.3 ms
11tick (ox_inventory)3470.595 ms156.6 ms
12tick (webpack)3420.020 ms26.3 ms
13thread @monitor/resource/sv_main.lua[484..489]3210.202 ms23.1 ms
14thread @monitor/resource/sv_main.lua[490..495]3210.095 ms18.9 ms
15event ox_lib:validateCallback [@ox_lib/resource/callbacks/shared.lua[55..65]]2910.016 ms8.1 ms
16thread @monitor/resource/sv_main.lua[482..487]2630.172 ms78.8 ms
17thread @monitor/resource/sv_main.lua[488..493]2630.079 ms58.0 ms
18thread @ox_lib/imports/callback/server.lua[63..63]2430.024 ms20.9 ms
19event:ox_inventory:closeInventory (ox_inventory)2420.280 ms46.6 ms
20event:__ox_cb_ox_inventory:openInventory (ox_inventory)2280.504 ms51.0 ms
21tick (cd_easytime)2170.062 ms3.0 ms
22event:__ox_cb_ox_inventory:useItem (ox_inventory)2120.555 ms79.8 ms
23event:ox_inventory:usedItemInternal (ox_inventory)2070.611 ms23.1 ms
24event:pma-voice:setTalkingOnRadio (pma-voice)2030.219 ms5.6 ms
25event:__ox_cb_ox_inventory (ox_inventory)1990.535 ms45.9 ms
26event:playerConnecting (monitor)1780.158 ms1.1 ms
27tick (rcore_casino)1760.101 ms43.0 ms
28event:__ox_cb_ox_inventory:swapItems (ox_inventory)1741.590 ms44.6 ms
29event:playerJoining (monitor)1710.298 ms8.9 ms
30event playerJoining [@monitor/resource/sv_playerlist.lua[138..168]]1700.214 ms8.6 ms
31tick (screencapture)1670.030 ms26.8 ms
32event:ox_inventory:updateWeapon (ox_inventory)1650.591 ms57.3 ms
33tick (rcore_pool)1630.033 ms1.3 ms
34tick (cd_dispatch)1620.172 ms3.1 ms
35event:chatMessage (monitor)1610.162 ms7.2 ms
36event:esx_status:update (esx_status)1600.778 ms63.3 ms
37thread @monitor/resource/sv_initialData.lua[28..39]1590.042 ms0.7 ms
38thread @cd_easytime/server/server.lua[338..349]1580.052 ms0.9 ms
39thread @cd_easytime/server/server.lua[321..336]1530.014 ms0.2 ms
40event:ox_inventory:usedItem (lb-phone)1520.066 ms1.9 ms
41event:entityRemoved (drugs_creator)1510.084 ms19.2 ms
42event:jg-vehiclemileage:server:update-mileage (jg-vehiclemileage)1502.256 ms268.5 ms
43event entityRemoved [?[41..46]]1500.015 ms6.0 ms
44tick (lb-phone)1470.454 ms15.8 ms
45event:txsv:startedWalking (monitor)1470.158 ms1.6 ms
46event:phone:togglePhone (lb-phone)1440.214 ms6.2 ms
47thread @cd_easytime/server/server.lua[261..271]1440.013 ms0.3 ms
48event:esx:triggerServerCallback (es_extended)1401.716 ms571.5 ms
49tick (drugs_creator)1380.739 ms96.3 ms
50event:playerDropped (monitor)1380.211 ms2.3 ms
51event playerDropped [@monitor/resource/sv_admins.lua[98..100]]1380.006 ms0.2 ms
52event:playerJoining (pma-voice)1360.387 ms8.8 ms
53event playerDropped [@monitor/resource/sv_playerlist.lua[170..194]]1350.093 ms2.2 ms
54event:ox_inventory:usedItem (drugs_creator)1330.281 ms6.7 ms
55event:__ox_cb_illenium-appearance:server:GetPlayerAces (illenium-appearance)1320.139 ms33.2 ms
56thread @monitor/resource/sv_main.lua[426..465]1320.099 ms3.1 ms
57thread @monitor/resource/sv_initialData.lua[24..35]1310.045 ms4.9 ms
58tick (rcore_radiocar)1300.052 ms4.1 ms
59event __ox_cb_ox_inventory:openInventory [@ox_lib/imports/callback/server.lua[121..123]]1280.692 ms51.0 ms
60tick (rahe-speakers)1280.064 ms27.5 ms
61thread @cd_easytime/server/server.lua[273..283]1260.015 ms0.6 ms
62event playerJoining [@ox_lib/imports/addCommand/server.lua[29..31]]1220.736 ms19.8 ms
63event:txsv:checkIfAdmin (monitor)1220.342 ms8.7 ms
64tick (es_extended)1191.156 ms131.8 ms
65event:__ox_cb_jg-mechanic:server:retrieve-and-apply-veh-statebag-data (jg-mechanic)1190.389 ms14.8 ms
66event:playerJoining (ox_inventory)1160.112 ms1.4 ms
67event:__ox_cb_jg-mechanic:server:save-veh-statebag-data-to-db (jg-mechanic)1150.416 ms20.4 ms
68tick (jobs_creator)1130.315 ms208.4 ms
69tick (jg-advancedgarages)1110.126 ms6.3 ms
70event __ox_cb_ox_inventory:useItem [@ox_lib/imports/callback/server.lua[121..123]]1100.453 ms43.2 ms
71event:playerDropped (pma-voice)1090.146 ms1.3 ms
72tick (EasyAdmin)1080.102 ms106.3 ms
73tick (cdev_pets)1080.210 ms5.9 ms
74tick (rcore_prison)1060.238 ms49.2 ms
75event:txsv:logger:deathEvent (monitor)1060.137 ms3.0 ms
76tick (rcore_golf)1040.046 ms1.6 ms
77event __ox_cb_ox_inventory [@ox_lib/imports/callback/server.lua[13..21]]1030.376 ms45.8 ms
78tick (rtx_dj)1030.116 ms26.9 ms
79event:txsv:logger:menuEvent (monitor)1030.056 ms0.4 ms
80event txsv:checkIfAdmin [@monitor/resource/sv_admins.lua[38..94]]1020.230 ms8.5 ms
81event:explosionEvent (monitor)1020.131 ms1.2 ms
82event explosionEvent [@monitor/resource/sv_logger.lua[89..102]]1020.013 ms1.1 ms
83tick (Renewed-Weathersync)1010.187 ms3.7 ms
84event:playerJoining (ox_doorlock)1010.088 ms1.0 ms
85tick (connectqueue)1000.108 ms4.2 ms
86tick (qbx_smallresources)990.107 ms10.1 ms
87tick (rtx_tv)972.853 ms140.4 ms
88event __ox_cb_ox_inventory:swapItems [@ox_lib/imports/callback/server.lua[121..123]]971.680 ms44.5 ms
89tick (ox_doorlock)960.586 ms932.9 ms
90thread @ox_lib/init.lua[136..147]961.490 ms97.0 ms
91event:pma-voice:setPlayerRadio (pma-voice)960.297 ms7.8 ms
92event:entityRemoved (cdev_pets)950.059 ms2.5 ms
93event:playerDropped (ox_inventory)940.494 ms30.7 ms
94tick (WaveShield)930.092 ms53.1 ms
95tick (vertex-hub)930.025 ms4.1 ms
96thread @Renewed-Weathersync/server/time.lua[22..33]930.207 ms3.7 ms
97tick (cs-hall)920.670 ms8.1 ms
98event:__ox_cb_jg-vehiclemileage:server:get-mileage (jg-vehiclemileage)913.503 ms176.6 ms
99tick (cron)900.090 ms13.2 ms
100thread @monitor/resource/sv_main.lua[424..463]890.127 ms1.0 ms

Client crash modules

From 61 deduplicated crash dumps uploaded to our crash analyzer. This sample is small and mostly inconclusive — the large majority resolve to fivem.exe itself with no specific faulting module, which tells you little. It is published for completeness, not as a finding.

FiveM crash reports by faulting module
Faulting moduleReports
fivem.exe48
citizen-devtools.dll2
gta-streaming-five.dll2
rage-graphics-five.dll2
adhesive.dll1
amdxx64.dll1
citizen-scripting-core.dll1
d3d11.dll1
glue.dll1
legitimacy.dll1
repscripts.exe1

Methodology

  • Collection. Profiler dumps voluntarily uploaded to our free FiveM profiler analyzer. No server identity, IP, or player data is stored or published — only resource names and their timings.
  • Deduplication. Each upload is hashed by the content of its resource list, so the same server re-uploading does not inflate server counts.
  • Exclusions. Engine-internal entries are filtered at ingest — the resource manager tick, anonymous threads, reference calls, task iterations, and CFX-internal events.
  • Definitions. Avg per tick is the mean CPU milliseconds the resource consumed per server tick. Worst tick is the single highest value observed. Servers is the count of distinct deduplicated profiles containing that resource.
  • Coverage. 2026-03-06 to 2026-10-05, 191,575 measurements, 674 servers. This page regenerates daily.
  • Licence. CC BY 4.0 — reuse it with attribution. Corrections and data requests to [email protected].

Questions

Which FiveM resource uses the most CPU?
Measured across 674 profiled servers, the resource with the highest mean per-tick cost among those running on 25 or more servers is tick (ox_stashdurability) at 31.124 ms average. The highest single tick ever recorded in this dataset is 1268.1 ms from event:QBCore:Server:TriggerCallback (qb-core). Mean cost and worst-case spike are different problems: a resource that is persistently expensive drags every frame, while a spike causes a visible hitch.
Is oxmysql slow?
oxmysql is the most widely deployed database resource in this dataset, appearing on 605 of 674 profiled servers. Its average per-tick cost is low at 0.093 ms, but its worst recorded tick is 1023.9 ms — roughly a full second. That pattern is characteristic of a resource that is cheap in normal operation and occasionally blocks on a slow query. The usual cause is an unindexed query or a synchronous call in a hot path, not oxmysql itself.
How many FiveM servers run ESX versus QBCore?
In this sample of 674 servers, 215 carry an es_extended (ESX) resource, 89 carry qb-core, and 112 carry qbx_core (Qbox). Note this counts servers where a resource name matches, which is a proxy for framework use rather than a declared dependency, and the sample is self-selected — see the limitations below.
Where does this FiveM performance data come from?
From profiler dumps voluntarily uploaded to GoodLeaf's free FiveM profiler analyzer at /analyze. Each upload is deduplicated by a content hash of its resource list so the same server re-uploading does not inflate the counts. The dataset currently holds 191,575 individual resource timings from 674 distinct servers, covering 2026-03-06 to 2026-10-05.
Can I use this data?
Yes. The full table is available as a CSV download and the data is published under CC BY 4.0, so you may reuse it with attribution to GoodLeaf Hosting. If you are writing about FiveM performance and want a figure checked or a cut of the data we have not published, email [email protected].

Profile your own server

This data is useful for comparing resources, but it cannot tell you what is wrong with your server. Upload a txAdmin profiler dump to get a graded report and your own worst offenders ranked. Free, no account, and you do not need to host with us.

GoodLeaf icon
4.6 / 5average of 199 reviews on Trustpilotlast checked

© 2017-2026 GoodLeaf Hosting & Development LLC. All rights reserved.

GoodLeaf Hosting & Development LLC is an independent provider of server infrastructure. We are not affiliated with GoodLeap financing or GoodLeaf vertical farming. We focus exclusively on High-Performance Game Hosting and Enterprise VPS solutions.