Built around the workload
Give your game server
the right kind of headroom.
A player count alone cannot size a server. Scripts, plugins, world data, databases and the players' network paths all affect the result.
01 / PROCESSORKnow the CPU behind it
Our host uses AMD EPYC 4564P: 4.5 GHz base and up to 5.7 GHz boost. VM performance also depends on contention and your software; clock speed is not a player-capacity guarantee.
AMD specifications ↗02 / MEMORY & STORAGEBudget for the full stack
Leave memory for your game process, database and operating system. NVMe storage supports your world files, logs and application data; actual I/O performance depends on the workload.
03 / NETWORKProtect the route
Gcore filters traffic upstream of the protected guest network. Choose a location for your players and test latency and jitter before committing to a game workload.
Explore protection ↗04 / VISIBILITYFollow real usage
The server dashboard provides CPU, memory and inbound/outbound network history from the hypervisor. Use those readings alongside your game's own profiling tools.
Explore the dashboard ↗