A server with 32 GB of RAM: when this much is enough and which hardware to choose
32 GB is the first size at which a dedicated server clearly differs from an ordinary VPS: all the memory is yours, and it is enough for a database, 1C (a popular Russian accounting suite) or several game worlds at once. As of 6 November 2026 the selection holds 1,089 plans from 98 hosts with exactly 32 GB of memory. The median is about $174 a month, a quarter of the plans cost less than $118, and another quarter more than $280. Most offers are in the US, Russia, Germany, Canada and France.
Workloads that 32 GB can handle
- A database for a mid-sized project. PostgreSQL recommends starting with 25 % of memory for
shared_buffers: on 32 GB that is 8 GB, and the database uses the rest through the operating system cache. For MySQL on a dedicated server the InnoDB buffer pool is usually set to 50–75 % of memory, that is 16–24 GB. If the database working set is 15–20 GB, it will sit almost entirely in memory. Similar configurations on VPS are in the servers for databases selection. - 1C. A 1C server and a DBMS (MS SQL or PostgreSQL) on one machine share the memory: the database takes it for cache, the 1C worker processes for user sessions. For a small company 32 GB is usually enough; the more users and the larger the database, the sooner such a server runs out of memory.
- Game servers. One modded Minecraft server needs about 8 GB, Rust 12 GB or more, ARK or Palworld about 16 GB. 32 GB fits two or three such worlds with room left for the system. Hardware for games is in the dedicated servers for games selection.
- Several virtual machines. Three or four machines with 6–8 GB each under Proxmox or Hyper-V: for example, separate machines for the website, the database and a test environment. The hypervisor itself needs 2–4 GB, and if storage is on ZFS, cap the size of its ARC cache, or it will take the memory you meant to give the machines.
- Caches and queues. Redis or Memcached with 10–20 GB next to the application. Leave headroom for Redis: when it saves a snapshot to disk it forks the process, and under heavy writes memory use grows for a while.
Where 32 GB is the ceiling and where it is only the start
The same capacity means different things on different platforms. About one plan in six in the selection runs on Intel Xeon E3 of the first three generations (E3-1230 v2, E3-1270 v3 and the like) or on Core i7 up to and including the 4th generation. For these processors 32 GB is the most the platform supports: you cannot add memory, only move to another server. On the other hand, these are the cheapest 32 GB in the selection, with a median of about $119.
Xeon E3 v5 and v6, Xeon E-2100 and 6th–8th generation Core take up to 64 GB; Ryzen 3000 and newer and EPYC 4004 take more. If the database is growing, ask the host whether there are free slots and what an upgrade costs: that is cheaper than moving.
Another quarter of the plans run on Xeon E5, often dual-processor. Xeon E5-16xx and E5-26xx have four memory channels each: if 32 GB is made of four 8 GB modules, every channel is populated, and bandwidth is higher than with two 16 GB modules on a desktop platform. But the processors themselves date from 2012–2017 and are behind new ones in single-core speed. The host can tell you how many modules the server has, even if the plan does not say.
ECC: do you need it at this size
Error-correcting memory (ECC) fixes single-bit errors that without it can silently corrupt a database record or a file. Server platforms on Xeon and EPYC are designed for ECC memory, and servers built on them almost always have it. On Ryzen, ECC works only if the motherboard supports it and the host has fitted such modules. Core i7 and i9 before the 12th generation have no ECC at all.
For a game server or a test environment this is not critical. If the server holds a database with payments, orders or 1C accounting records, choose a platform with ECC and ask the host which modules are installed.
How to compare processor, disks and price
Nearly all of the price difference between 32 GB plans comes from the processor and disks. 40 % of the plans in the selection have four cores or fewer: usually enough for a database or 1C, already too few for virtual machines and several game worlds. For games, clock speed matters more: look at processors from 3.5 GHz and current Ryzen.
The most common disks in the selection are SATA SSD, in about half of the plans; another third use HDD, and NVMe is in roughly one in eight. For a database or 1C a hard disk is the main bottleneck, even with enough memory: reads and writes of whatever does not fit in the cache still go to disk. If you need a fast disk, see dedicated servers with NVMe.
Compare plans this way: first rule out processors that cannot handle your load, then choose the disk type, and only then compare the price. Old hardware is not always cheaper: in the selection, mid-range Ryzen plans with NVMe cost about $153, while Xeon E3 v3 plans with hard disks cost about $203. The memory is the same, but the second server is slower in both processor and disk.
If 32 GB is already tight, compare servers with 64 GB: the median there is about $73 a month higher. If you do not need a dedicated server yet, look at VPS with 32 GB of memory or more: they are cheaper, but the processor and disks are shared with other customers.