How to choose a dedicated server: CPU, RAM, NVMe

You choose a dedicated server based on what your application does: a CPU with high clock speed or many cores, enough ECC RAM, NVMe storage in RAID, the right uplink, Anti-DDoS included, and a clear decision on who manages it. You don't need to be an engineer to get it right. Below I go through each spec and how to size it.

CPU: cores or clock speed

You pick the processor based on the kind of application. Two things matter: the number of cores and the clock speed (GHz) per core.

• High per-core clock speed helps applications that do most of their work on one thread: many game servers, some database processes, sequential jobs.
• Many cores help when you run lots of processes in parallel: an online store with many simultaneous visitors, virtualization, several applications on one server.

Don't look only at the core count. For single-thread work, a CPU with 8 fast cores can beat one with 32 slow cores. Think about what your application spends most of its time doing and choose accordingly.

RAM: how much, and why ECC

RAM holds your applications' active data. Too little means swapping to disk and sudden slowdowns; too much is money wasted. Rough guidelines:

• Mid-sized sites and stores: 16-32 GB covers an active online store with caching.
• Heavy databases, many applications, virtualization: 64 GB or more.
• Modded game servers: depends heavily on the game and player count, but leave headroom for peaks.

The type of memory matters too. ECC (Error-Correcting Code) memory detects and fixes errors automatically before they corrupt data. On a server running nonstop for weeks, I wouldn't skip ECC: it protects you from crashes that are hard to explain.

Storage: NVMe vs SSD vs HDD, and what RAID does

Storage decides how quickly the server responds. You have three options:

• HDD: mechanical drives, slow but cheap per terabyte. Fine for archives and backups, not for active applications.
• SSD (SATA): much faster than HDD, capped by the SATA interface at roughly 550 MB/s.
• NVMe: uses the PCI Express bus directly, reaches several GB/s, with microsecond latency and hundreds of thousands of IOPS. The normal choice for fast applications.

For any active application (site, store, database), go with NVMe; you feel the difference on every request. Keep HDDs for large backups.

RAID: speed and safety

With a single drive, one failure stops everything. RAID combines several drives for redundancy, performance or both:

• RAID 1: mirroring, the same data on two drives, so one failed drive doesn't stop you.
• RAID 10: speed plus redundancy, recommended for databases and important applications.

If you can't afford to lose data, you need RAID. Always ask which RAID level is included.

Bandwidth and uplink: unmetered or fair use

The word "bandwidth" usually covers two different things:

• Uplink (the network port): the maximum connection speed, for example 1 Gbps or 10 Gbps. It decides how fast you can deliver data.
• Monthly traffic: the total volume of data transferred. It can be metered or "unlimited".

Be careful with unlimited: it nearly always comes with a fair-usage policy. Read it to avoid surprises. For most projects a 1 Gbps uplink with generous traffic is enough; heavy-transfer applications (streaming, large downloads) need more.

Anti-DDoS: ask for it from the start

A DDoS attack can take your server offline however powerful the hardware, because it floods your connection with hostile traffic. Network-level Anti-DDoS filters that traffic before it reaches the server and keeps it available during the attack.

Ask whether Anti-DDoS is included, at what capacity, and whether it kicks in automatically. For online stores, game servers and any public service, you need it.

Managed or unmanaged: who runs the server

A dedicated server can come bare or with management included. Choose based on your skills:

• Unmanaged: you get the server and handle installation, hardening, updates and monitoring yourself. It costs less, but you need sysadmin knowledge.
• Managed: the provider does the heavy lifting while you look after your application. It costs more, but saves time and avoids expensive mistakes.

If you don't have a technical team, a managed or at least assisted setup is worth the extra cost.

IP addresses: how many you need

Most servers come with at least one public IP address. You need more if you host services that require separate IPs, IP-bound SSL certificates, or you want to isolate certain applications. Ask how many IPs are included and what extra ones cost.

Checklist before you order

• A CPU that fits the application: per-core speed or core count, depending on the workload
• Enough RAM, ECC type
• NVMe storage for active applications, with RAID for redundancy
• The right uplink, and the traffic policy read carefully
• Anti-DDoS included, with real capacity
• Managed or unmanaged, depending on your skills
• The number of IPs you need
• The server location, for low latency to your users

How BTU helps you choose

At BTU you'll find dedicated servers with NVMe storage, ECC memory, RAID for redundancy, network-level Anti-DDoS and a good uplink, and each configuration lists its exact specs. You can pick EU locations for low latency and GDPR. You get support in Romanian and help with sizing; if you also want help with management, tell us up front. If you're still torn between dedicated and something scalable, read the comparison VPS vs dedicated server vs cloud or the guide on how much resource a site needs.

Browse the dedicated servers, check the cloud options if your traffic fluctuates, and tell us what you're building. We'll recommend a configuration without resources you don't need.