VPS on AMD Ryzen: what a desktop processor brings to a server and what you pay for it
Ryzen was designed for workstations and gaming PCs, not for data centre racks. Hosts still readily put it in servers: a Ryzen core runs at clock speeds that server EPYC and Xeon chips usually don't reach, and the platform itself is cheaper. For the buyer, a VPS on AMD Ryzen is a fast single-threaded processor for moderate money, but with quirks that plan descriptions rarely mention.
Why gaming and single-threaded workloads love Ryzen
A game server, a 1C server (a Russian accounting platform), a trading terminal, a PHP website without caching: all of these are programs whose main loop runs in one thread. What matters to them is core clock speed, memory latency and cache size, not the number of cores. Recent Ryzen generations sustain 5 GHz and more under load, and the X3D versions carry an enlarged L3 cache that is especially good at speeding up game worlds with many objects. The general principles of choosing a high-frequency plan are covered on the VPS with a high clock speed page, and the requirements of game projects in the VPS for game servers selection.
Generation matters more than the name. Ryzen 3000 series (Zen 2) and Ryzen 7000 and 9000 series (Zen 4 and Zen 5) are processors of different speeds, even though in a plan they may all be called simply "Ryzen". The per-core difference between an old and a recent generation reaches one and a half to two times. If the model isn't stated in the description, ask support before paying.
How many cores to take also depends on the task. A game server or 1C usually manages with 2–4 vCPUs: one core goes to the main thread, the rest to the system, the database and background jobs. More cores on Ryzen make sense if the server runs several independent processes, such as several game worlds or copies of an application. Remember that a vCPU on Ryzen, as on any processor with SMT, usually equals one thread rather than a whole physical core: two threads of one core share its execution units, and under full load each of them is slower than a single one.
How a desktop platform differs from a server one
- Memory without ECC. Ryzen chips themselves can work with ECC memory, but this depends on the motherboard, and budget servers often don't have it. Without error correction, a rare bit flip can corrupt data in memory or crash the system. For a game server this is unpleasant; for a database holding customers' money it is a serious risk.
- Two memory channels. A desktop platform has two channels versus eight to twelve on a server one. When dozens of virtual machines run on one node, memory bandwidth is shared among them all, and memory-heavy tasks slow down.
- Fewer cores per node. 12–16 cores versus 64 or more on EPYC. To make the server pay off, a host may pack the node densely, and then the high clock speed is eaten up by neighbours. Keep an eye on steal time.
- Simplified hardware. One power supply, no board-level remote management, not always hot-swappable disks. A node failure is fixed by an engineer by hand, and downtime can be longer.
- Temperature. Ryzen is designed for high clock speeds with good cooling. In a cramped chassis the processor drops its clock speed under sustained load, and you will see the peak figures from the description only in short tests.
Tasks for which Ryzen is not the best choice
If a project needs a lot of RAM, many cores or predictable round-the-clock operation without the risk of in-memory data corruption, look at server processors. VPS on AMD EPYC give fewer gigahertz per core but more cores and memory channels, and almost always ECC. Another high-frequency alternative is VPS on Intel Core, with its own architectural quirks. For a large database, virtualisation inside a VPS or a container cluster with dozens of services, a server platform is usually more reliable.
How to check a plan after buying
- Run
lscpuand look at the Model name line. Some hosts show the guest a generic processor name; in that case rely on benchmarks. - Run
sysbench cpu --threads=1 runseveral times during the day. A large spread in results points to an overloaded node or throttling. - Watch the
stcolumn intopunder load: consistently above a few per cent means neighbours are taking CPU time. - For a game server, start a real world with bots or test players and look at the tick time; synthetic tests don't show everything.
Use a trial period or a refund if the plan offers them: checking the processor in the first day is easier than moving a month later.