Ryzen 7 3700X Dedicated Server

What this server gives you

Fiziksel 1 (Ryzen) is a single-tenant machine running in our own cabinets at the DGN Data Centre in Bursa, Türkiye. Every core of the AMD Ryzen 7 3700X 3.60 Ghz processor, all 64 GB DDR4 RAM of memory and the 500 GB NVMe SSD / 1 TB NVMe SSD of storage are reserved for your workload alone; no other customer's processes run on the same hardware. Because there is no virtualisation layer in between, CPU scheduling, disk queueing and memory access are unaffected by neighbouring load. In practice that means response times stay consistent through the day for latency-sensitive work such as databases, build servers and game hosting.

Which workloads this hardware suits

The AMD Ryzen 7 3700X 3.60 Ghz processor together with 64 GB DDR4 RAM of memory is a measured combination for PostgreSQL or MySQL installations that can hold the entire hot data set in memory, for panel installations hosting several game server instances on one machine, for CI/CD build queues and for video encoding jobs. The 500 GB NVMe SSD / 1 TB NVMe SSD of NVMe storage does not collapse in random read and write performance as queue depth grows, the way spinning disks do; that is why it is preferred for workloads producing many small concurrent writes, such as logging, session stores and game save files. For applications bound to a single thread it is the processor's turbo frequency rather than the core count that decides throughput; the hardware table below lists base and turbo figures together.

Network, transit capacity and DDoS protection

The server is placed in Bursa, Türkiye with a 1 Gbps Internet / 10 Gbps Internet connection. The backbone the cabinets attach to runs over a redundant uplink; transit capacity is 100 Gbps domestic and 10 Tbps international. If you serve users in Türkiye, a domestic egress gives noticeably lower latency than a location abroad. All traffic passes behind the Fexwall layer: DPDK-based L3/L4 filtering drops packets built with spoofed source addresses at the edge of the network and keeps volumetric attacks away from the server's network interface. This protection is not a separately sold package but part of the service; project-specific rules are defined from the Fexwall section of the customer panel.

Storage layout and backup responsibility

The 500 GB NVMe SSD / 1 TB NVMe SSD of storage arrives ready at handover; you can state the disk layout you want — a single disk, software RAID or a separate data disk — in your installation request. Dedicated servers sit outside the automatic snapshot infrastructure, and this is the most frequently overlooked difference from a virtual server. Because backup responsibility is yours, critical data should not live only on this machine: take regular copies to a second Datafex server, to your own location or to external object storage. Keeping the backup on the same disk means losing both the original data and the backup in a single disk failure.

Dedicated server or virtual server?

On a virtual server the resources of one physical machine are divided by a virtualisation layer; vCPU, RAM and disk are reserved for you, but the hardware is shared. A dedicated server has no such layer: every core of the AMD Ryzen 7 3700X 3.60 Ghz processor is visible directly to your operating system, you get full access to the disk controller, and you can install your own virtualisation (KVM, Proxmox, Hyper-V) on top of this machine. Scaling works differently in return: on a virtual server a resource increase takes minutes from the panel, while adding RAM or disk to a dedicated server requires hardware work and a short maintenance window. Starting on a virtual server is more flexible for a project whose resource needs have not settled; for workloads with a known and steadily high demand, a dedicated server is more predictable.

The delivery process

Dedicated servers are handed over through a manual process rather than automatic provisioning. You can follow every step from the service detail page in the customer panel.

1. 1Order and payment: pick the location and operating system in the configurator and place the order.
2. 2Hardware allocation: once payment is confirmed the in-stock machine is reserved for you, mounted in the cabinet and checked.
3. 3Operating system installation: the Linux distribution or Windows Server edition you chose is installed clean.
4. 4Network configuration: an IP address is assigned and the server's traffic is moved behind the Fexwall filtering layer.
5. 5Handover: access details are shared on the service detail page in the customer panel and the server is ready to use.

Common mistakes when choosing

• Looking only at the core count. For applications bound to a single thread — most game servers, some reporting queries — turbo frequency decides more than the number of cores.
• Sizing memory from the application's momentary usage. The file system cache uses RAM too; a database that cannot hold its whole hot data set in memory falls back to disk, and even NVMe does not fully close that gap.
• Leaving backups for later. There is no automatic snapshot on a dedicated server, so the backup routine should be in place from day one, before the data grows.
• Confusing port speed with real throughput. The 1 Gbps Internet / 10 Gbps Internet figure on the interface is the machine's link port; the speed you reach in a single session also depends on the far end's capacity, on latency and on packet loss.

Other dedicated servers

Other hardware options in the same data centre.

• Fiziksel 1 (Intel) Dedicated Server
• Fiziksel 2 Dedicated Server
• Fiziksel 3 Dedicated Server