
You are picking a host, a VPS or your own hardware for a FiveM server, and you want to know which CPU to look for and why. Cfx.re says very little about it. Its server hosting FAQ recommends "a x86-64 system running Linux or Windows (7/2008 R2+), decent upstream connectivity and preferably a multi-core processor", and that is the whole official recommendation. The rest of the answer sits in FXServer's open source code, which shows how the server splits its work over threads and how often each thread has to run. This guide reads that code, puts AMD's published specs side by side, and shows how to check whether the CPU is really what slows your server down before you pay for a faster one.
Quick answer: The best CPU for a FiveM server is a current-generation x86-64 processor with the highest single-core boost clock in your budget, plus a few cores to spare. Per-core speed matters more than core count because FXServer runs the resource tick, where your server scripts do their work, on one main thread (svMain) that is meant to tick every 50 ms. A Ryzen 9 9950X, for example, boosts to 5.7 GHz on one core by AMD's spec sheet, where the 24-core EPYC 7443 server chip reaches 4.0 GHz. Extra cores keep the network thread, the OneSync sync thread and your database from competing with the main thread, but they cannot split it. Before you buy a faster CPU, look for "server thread hitch warning" in the console and record a profile: a slow script hitches on any CPU.
What the Best CPU for FiveM Has to Do
FXServer is not one loop. In GameServer.cpp (citizenfx/fivem, master branch, last changed 24 June 2026) the server starts three timed loops, and UvLoopHolder.cpp gives each loop its own thread, named luv_svMain, luv_svNetwork and luv_svSync on Linux and UV loop: svMain and so on on Windows. These are the timers and warnings in the code:
| Thread | Timer in the code | Runs every | What runs on it | Console warning |
|---|---|---|---|---|
| svMain | 1000 / 20 | 50 ms, 20 times a second | The server frame: client timeouts, the server list heartbeat, then the resource tick that runs your scripts | server thread hitch warning when a gap passes 150 ms |
| svNetwork | 1000 / 100 | 10 ms | Processing incoming and outgoing network packets | network thread hitch warning when a gap passes 150 ms |
| svSync | 1000 / 120 | 8 ms (integer maths) | OneSync's game state tick, only when OneSync is on | sync thread hitch warning when a gap passes 100 ms |
The line that matters most is in ServerResources.cpp: the server's OnTick event, which fires at the end of every svMain frame, calls the resource manager's Tick(). That is where your Lua, JavaScript and C# resources get their server-side tick, so the script work done in those ticks shares one thread and one 50 ms budget.
Two notes on the table. The sync rate is the public source code. FiveM for GTAV Enhanced has a sv_syncTickRate setting with a default of 60 and a range of 1 to 120, and Cfx.re's Enhanced changes page says "Higher values can reduce latency but increase CPU usage." The same GameServer.cpp also contains an older network loop that prints hitch warning: net frame time of %d milliseconds, but that loop only runs when the network layer does not use libuv. The ENet layer, which a comment in GameServer.cpp calls the only one supported "at this time", does use it, so on current builds you should see the three warnings in the table.
Single-Core Speed vs Core Count
A tick on svMain has 50 ms. Everything in that frame, every resource's tick included, has to finish before the next tick can start, because it all runs on one thread. A worked example:
- Your resources and the rest of the frame take 30 ms. The thread is idle for 20 ms and the server keeps its 20 ticks a second.
- They take 80 ms. The next tick can only start when that work is done, so the server manages about 1000 / 80 = 12.5 main ticks a second instead of 20. No warning appears yet, because the warning starts at 150 ms.
- One tick takes 400 ms, for example because a script does a large job in one go. The console prints
server thread hitch warning: timer interval of 400 millisecondsor close to it: 400 / 50 = 8 tick intervals passed where one was due.
A faster core shrinks those numbers. More cores do not, because a 16-core and a 4-core CPU with the same per-core speed finish one svMain tick in the same time. Cores still count for everything around it: svNetwork and svSync are separate threads that tick far more often than svMain, and your database (MySQL or MariaDB) runs as its own process. That is why Cfx.re recommends "preferably a multi-core processor", and why a fast CPU with too few free cores can still stutter.
On a shared host the same thing applies one level up: your server's threads share physical cores with other servers on that machine. Ask how many cores your plan gets and whether they are shared.
AMD CPUs for FiveM, Compared on Paper
These specs come from AMD's own product pages, opened on 4 November 2026. They are not benchmarks: neither AMD nor Cfx.re publishes FXServer results per CPU, and we have not measured them.
| CPU | Cores / threads | Base clock | Max boost | L3 cache | Memory | Launched |
|---|---|---|---|---|---|---|
| Ryzen 9 9950X (Zen 5) | 16 / 32 | 4.3 GHz | Up to 5.7 GHz | 64 MB | DDR5 | 15 Aug 2024 |
| Ryzen 9 7950X3D (Zen 4) | 16 / 32 | 4.2 GHz | Up to 5.7 GHz | 128 MB | DDR5 | 28 Feb 2023 |
| Ryzen 9 5950X (Zen 3) | 16 / 32 | 3.4 GHz | Up to 4.9 GHz | 64 MB | DDR4 | 5 Nov 2020 |
| Ryzen 9 3900X | 12 / 24 | 3.8 GHz | Up to 4.6 GHz | 64 MB | DDR4 | 7 Jul 2019 |
| EPYC 7443 (server) | 24 / 48 | 2.85 GHz | Up to 4.0 GHz | 128 MB | DDR4 | 15 Mar 2021 |
How to read it for a FiveM server:
- Max boost is the number closest to svMain. AMD defines it as "the maximum frequency achievable by a single core on the processor running a bursty single-threaded workload", and adds that it varies with cooling, motherboard, BIOS and other factors. On a node where many servers run at once, do not expect every core to hold it.
- Clock speeds compare cleanly only within one generation. The 9950X, 7950X3D and 5950X are three generations (Zen 5, Zen 4 and Zen 3 on AMD's pages). Across generations, look at single-thread test results from a source you trust instead of the GHz figure.
- The extra cache on the 7950X3D is unproven for FiveM. It has twice the L3 cache of the 9950X at the same max boost. Without published FXServer results, treat it as a maybe, not a reason to pay more.
- A server chip trades boost for cores. The EPYC 7443 has 24 cores but boosts to 4.0 GHz. Many cores at a lower clock suit many small servers on one machine. For one busy roleplay server whose scripts all run on svMain, the higher boost of a desktop-class chip counts for more.
Is the CPU Really Your Bottleneck?
A faster CPU only helps when the main thread is short of CPU time. Check that in this order.
1. Read the console. The three warnings name the thread. The number in the message is the gap between two ticks of that thread, not the work done in one tick: server thread hitch warning: timer interval of 412 milliseconds means 412 ms passed where 50 ms was due. Note when the warnings come: at start, at peak player count, or each time one action runs in game.
2. Open txAdmin's thread chart. The txAdmin dashboard has a performance card titled "svMain performance" with a selector for svMain, svSync and svNetwork. It reads the tickTime histogram FXServer keeps for each thread, which records how long each tick spent working in buckets from 1 ms to 250 ms, and shows the share of time spent in each bucket. If much of svMain's time sits in the buckets near and above 50 ms, the main thread is out of budget even when no hitch warning prints. txAdmin's code waits for 600 ticks, 30 seconds of svMain, before it treats the data as reliable.
3. Record a profile. The profiler guide in Cfx.re's docs says the profiler works on the server console too:
profiler record 500
profiler status
profiler saveJSON cpu-check.json
500 frames is the guide's suggested starting point, and it says the saved file lands in the folder where your run.bat file lives. Open Chrome, press Ctrl+Shift+I, choose the Performance tab, right-click and load the file. Spikes in the yellow CPU time graph are the hitches. Zoom into one and the resource tick events show which resource, file and line used the time.
4. On a VPS, watch the threads. Run top -H and look for luv_svMain in the command column. If it sits close to 100% (one full core) while the machine as a whole still has CPU left, your server is limited by the speed of one core, and that is the case where a faster CPU helps. If the whole machine is at 100%, you need more cores or fewer things running on it.
When It Is Not the CPU
| What you see | What it points at | Next step |
|---|---|---|
| The profile shows one resource taking most of each tick | That script, on any CPU | Find and fix laggy resources |
oxmysql prints <resource> took <N>ms to execute a query! | A slow query: oxmysql logs every query at or above mysql_slow_query_warning, 200 ms by default | Fix the query or its indexes. With set mysql_ui true, admins with the command.mysql permission get an in-game mysql overview per resource |
| Memory climbs until the server dies | A leak, not the CPU | Memory leak guide and RAM sizing |
| The server crashes or restarts | Read the logs before you change hardware | Crash guide |
| Players lag but svMain's chart is calm | Check svSync and svNetwork in the same chart, and OneSync settings | OneSync explained |
Every resource gets slower at peak, none stands out, and luv_svMain is near 100% | The CPU is the limit | A faster per-core CPU, or fewer servers sharing it |
Playing FiveM: The CPU Your PC Needs
If you searched "best CPU for FiveM" to play rather than to host: your own PC renders the game, so your FPS depends on your processor and graphics card, not on the server's CPU. fivem.net lists these processors (checked 4 November 2026):
| Client | Minimum | Recommended |
|---|---|---|
| FiveM Legacy (GTA V Legacy) | Intel Core 2 Quad Q6600 2.4 GHz or AMD Phenom 9850 2.5 GHz | Intel Core i5 3470 3.2 GHz or AMD FX-8350 4 GHz |
| FiveM for GTAV Enhanced (early access) | Intel Core i7-4770 or AMD FX-9590 | Intel Core i5-9600K or AMD Ryzen 5 3600 |
Memory, graphics and disk are in our FiveM system requirements guide.
Renting a FiveM Server: What to Ask
Most owners rent rather than build. Ask a host three things: which CPU model your server runs on (a model number, not just "Ryzen" or "high frequency"), whether that CPU is shared with other servers on the node, and whether the hardware is the same in every region you can pick.
Our own FiveM servers run on the AMD Ryzen 9 9950X in the Netherlands, Germany and Poland, on the Ryzen 9 7950X3D in the USA, on the Ryzen 9 5950X in Singapore and Australia, and on Ryzen 9 3900X-class hardware in India. The CPU is shared with other servers on the node and the RAM is reserved for yours. If you would rather run FXServer and txAdmin yourself with root access, a Premium VPS runs on the Ryzen 9 9950X in an EU data center.
FAQ
Does FiveM use multiple cores?
Yes, but not for your scripts. FXServer runs svMain, svNetwork and svSync on three threads, and your database runs as its own process, so a multi-core CPU keeps them out of each other's way. Your resources all tick on svMain, so the speed of one core caps how much script work fits into each 50 ms tick, however many cores the machine has.
Intel or AMD for a FiveM server?
Either. Cfx.re recommends an x86-64 system, both brands make x86-64 processors, and nothing in that recommendation prefers one. Compare the CPU models you are actually offered on single-core speed, generation and whether the cores are shared, not on the brand.
Is X3D cache worth it for FiveM?
Not proven. The Ryzen 9 7950X3D has 128 MB of L3 cache against 64 MB on the 9950X, at the same 5.7 GHz max boost, but neither AMD nor Cfx.re publishes FXServer results for it, and we have not measured it. If you already run a server, profile it first: when one script eats the tick, fixing that script is the surer gain.
What does "server thread hitch warning" mean?
It means svMain, the thread that runs your resources, started a tick more than 150 ms after the previous one, where it should tick every 50 ms. The number is the gap: timer interval of 300 milliseconds means six ticks' worth of time passed in one gap. Either the work on that thread took too long, such as a slow resource the profiler can name, or the thread did not get CPU time because the machine was overloaded.
What is the best CPU for playing FiveM?
Cfx.re recommends an Intel Core i5 3470 or AMD FX-8350 for FiveM Legacy, and an Intel Core i5-9600K or AMD Ryzen 5 3600 for FiveM for GTAV Enhanced. Those are its recommended specs, not a ceiling; the system requirements guide covers memory and graphics too.
Can a FiveM server run on ARM?
Not officially. Cfx.re's server FAQ recommends an x86-64 system, and its setup guide names the Enhanced server downloads cfx-server_win_x64 and cfx-server-linux_x64. Our Oracle Cloud ARM post explains what goes wrong when you try anyway.
Sources
All opened on 4 November 2026:
- Cfx.re: server hosting FAQ, FiveM system requirements on fivem.net, What's Changed in FiveM for GTAV Enhanced, Using the Profiler, Setting Up a Vanilla FXServer
- FXServer source (citizenfx/fivem, master): GameServer.cpp, ServerResources.cpp, ServerGameState.cpp, GameServerNet.ENet.cpp, UvLoopHolder.cpp
- txAdmin source: ThreadPerfCard.tsx, svRuntime config.ts, perfParser.ts
- oxmysql source: config.ts, logger
- AMD: Ryzen 9 9950X, Ryzen 9 7950X3D, Ryzen 9 5950X, Ryzen 9 3900X, EPYC 7443