A Metin2 private server is not a single application but a set of cooperating processes: the db process holds the database cache, the auth process handles logins, separate game cores run for each channel, and MySQL/MariaDB sits underneath them. What determines resource needs is therefore not just the concurrent player count but the number of channels and cores you open. The second factor is that most original Metin2 binaries are still 32-bit and require 32-bit compatibility libraries on the distribution.
These values map one to one onto the VDS plan steps in our catalogue. Intermediate values can also be selected in the configurator.
| Players | RAM | vCPU | Storage | Intel i9-10920XDDR4 · Value | Ryzen 9 7950XDDR5 · Performance | Note |
|---|---|---|---|---|---|---|
| 1-300 | 8 GB | 4 | 80 GB | ₺1.410,00 / mo | ₺1.940,00 / mo | 1-2 channels x 4 cores with auth, db and MySQL all local. The typical starting point for newly opened servers. |
| 300-800 | 16 GB | 8 | 160 GB | ₺2.970,00 / mo | ₺4.000,00 / mo | 3-4 channels, a growing player table, an active marketplace and siege events. MySQL needs its own memory allocation here. |
| 800+ | 32 GB | 16 | 250 GB | ₺5.600,00 / mo | ₺7.630,00 / mo | A multi-channel setup. At this scale moving MySQL to a separate server is more effective than adding vCPU on the same machine. |
The amounts in the table are the monthly net price of each processor option and match the calculation in the configurator. The value option uses DDR4 memory, the performance option DDR5. Billing period (3, 6, 12, 24, 36 months) and extra resources are calculated in the configurator.
Prices exclude VAT (20%).
The practical calculation works like this: each game core takes 400-700 MB, the db process 500 MB-1.5 GB, auth 200-400 MB, and MySQL 2-6 GB depending on database size. A typical 2-channel x 4-core setup fills 8 GB once MySQL is included. On the CPU side, vCPU count is a real lever because each core runs on its own thread; the game loop inside a single core is single-threaded, however, so clock speed matters on a busy channel. On storage, MySQL binlog and player table growth need to be accounted for.
Most game servers run on a single thread, so per-core performance matters more than core count.
The value option. 12 cores / 24 threads with DDR4. Because Metin2's per-channel core processes spread across separate threads, core count helps directly, and this processor offers the most attractive per-resource pricing for multi-channel setups.
View plansThe performance option. Zen 4 with DDR5. Because the game loop inside a single channel is single-threaded, clock speed decides behaviour on a busy channel; and if MySQL runs on the same machine, DDR5 bandwidth shows up in query latency.
View plansPick the plan that matches your player count, choose the operating system and start provisioning within minutes.
Games that run on the same infrastructure with comparable resource needs. Each page lists RAM, vCPU and storage guidance by player count.
Server hardware and the operating system are included; the game's server software and any game licence are NOT included — you obtain and install those yourself. Our guides walk through the setup.
Game names and logos are property of their respective owners. Datafex is not an official partner or authorised reseller of these games.
