Choosing a server does not simply mean looking for the system with the most cores, the most memory or the largest number of drives. The right configuration depends on the workload, number of users, applications, expected growth, availability requirements and budget.

In this first part of Rukam's Server Buying Guide, we explain how to evaluate the three components that most strongly affect server behavior: processor, RAM and storage.

Before choosing a configuration

Before selecting a configuration, answer a few questions:

  • What will be the server's main role?
  • How many users or virtual machines will use the system?
  • Which applications and operating systems will run on it?
  • Does the workload require higher per-core performance or greater parallel processing capability?
  • How much memory does the application use today and what growth is expected?
  • Should storage prioritize capacity, performance, latency, redundancy or a combination of these factors?
  • Will future expansion be required?

There is no universally “best” configuration. There is a configuration that is better suited to the workload.

Rack, Tower or Blade

Before CPU, memory and drives, it is also important to define the physical platform:

  • Rack: the predominant format in data centers and technical rooms, offering good density, expansion and serviceability;
  • Tower: suitable for smaller environments without a rack or dedicated infrastructure;
  • Blade or modular: suitable for environments using a shared chassis and requiring high density.

Platform choice should consider space, expansion, power consumption, cooling, management and the infrastructure already available.

Processor (CPU)

The CPU executes instructions from the operating system, applications and server services. When comparing processors, the main points include:

  • number of cores;
  • base frequency and Turbo frequency;
  • processor architecture and generation;
  • number of processors supported by the platform;
  • supported memory and number of memory channels;
  • power consumption/TDP;
  • software licensing requirements.

A processor with a higher clock speed is not automatically faster in every application, just as a processor with many cores is not automatically the best choice. The workload determines which characteristic matters most.

Higher clock speed or more cores?

Workloads that depend mainly on a small number of threads may benefit more from high per-core performance. Virtualization, multiple simultaneous services and applications that can parallelize tasks may make better use of a larger number of cores.

For database servers, virtualization and applications licensed per core, the choice should also consider licensing, number of VMs, actual application behavior and CPU generation.

Processors should therefore be compared as part of complete platforms, rather than by looking only at GHz or core count.

Threads

Threads represent execution flows that a processor can handle. With technologies such as Intel Hyper-Threading, a physical core can expose more than one logical processor to the operating system.

This can improve the use of internal processor resources for certain workloads, but an additional thread is not equivalent to an additional physical core. The performance gain varies by application.

RAM

RAM holds data and instructions that need to be quickly available to the processor. In servers, the required amount depends directly on the application.

When sizing memory, consider:

  • operating system;
  • applications and databases;
  • number of users;
  • number and size of virtual machines;
  • application cache requirements;
  • expected growth;
  • headroom for utilization peaks.

In addition to total capacity, consider DIMM type, supported speed, memory-channel population, number of installed processors and platform-specific rules.

Installing more memory than the workload actually needs does not necessarily improve performance. The goal is sufficient capacity for the current workload, appropriate headroom and room for future expansion.

HDD or SSD?

HDDs and SSDs serve different purposes.

HDD remains an important option when the priority is large capacity at a lower cost per TB, especially for file storage, backup, repositories and predominantly sequential workloads.

SSD offers lower latency and higher I/O performance and is generally better suited to operating systems, virtualization, databases and applications with heavy random-access activity.

The two technologies can also be combined, using SSDs for performance-sensitive workloads and HDDs for high-capacity storage.

SATA, SAS and NVMe

The main storage interfaces found in Enterprise servers include:

  • SATA: widely used with HDDs and SSDs, usually prioritizing capacity and cost;
  • SAS: traditionally used in Enterprise environments, with features and characteristics aimed at servers and storage systems;
  • NVMe: uses PCI Express and provides much lower latency and high I/O capability when supported by the platform.

When choosing drives, check interface, backplane, controller, physical form factor, speed, capacity, compatibility and hot-swap support.

The nominal interface speed should not be confused with the actual performance of the drive. For example, SATA 6G and SAS 12G interfaces are expressed in Gb/s, not GB/s.

2.5" or 3.5"

Physical form factor also affects the configuration:

  • 3.5" (LFF): widely used when capacity per drive is the priority, especially with HDDs;
  • 2.5" (SFF): allows higher drive-bay density in many servers and is common with SAS HDDs, SATA/SAS SSDs and certain storage architectures.

The number and type of server bays should be considered together with required capacity, redundancy, future expansion and the installed controller.

RAID

RAID level is also part of server sizing.

RAID can provide redundancy, performance or a combination of both, depending on the level used. Choosing between RAID 1, RAID 5, RAID 6, RAID 10 or other options should take into account drive count, required usable capacity, write performance, fault tolerance and rebuild time.

It is important to distinguish:

  • raw capacity: the sum of the nominal capacity of all drives;
  • usable RAID capacity: space available after redundancy;
  • capacity presented by the operating system: may appear numerically lower because of the difference between TB and TiB, formatting and file-system structures.

Example 1 — File services, Active Directory and light applications

Possible platforms: Dell PowerEdge R720 / HPE ProLiant DL380 Gen8 or equivalent systems, when compatible with the application and support requirements.

  • 1 × Intel Xeon E5-2650 v2 — 8 cores / 16 threads, 2.60 GHz base;
  • 128 GB DDR3 ECC RDIMM, configured according to the platform's memory-population rules;
  • 4 × 4 TB Enterprise HDDs in a RAID level appropriate to capacity, performance and redundancy requirements;
  • RAID controller with cache and protection suitable for the configuration;
  • redundant power supplies when required by the environment.

The configuration should be validated according to the operating system, application, data volume, number of users and backup policy.

Example 2 — Virtualization, applications and mid-range databases

Possible platforms: Dell PowerEdge R730 / HPE ProLiant DL380 Gen9 or equivalent systems, according to application and support requirements.

  • 2 × Intel Xeon E5-2695 v4 — 18 cores / 36 threads per processor;
  • 256 GB DDR4 ECC RDIMM;
  • Enterprise SAS or SATA SSDs sized according to capacity and I/O workload;
  • RAID selected according to the required performance and fault tolerance;
  • controller, cache, power supplies and network interfaces compatible with the application.

For SQL Server, virtualization or other workloads licensed per core, processor selection should also consider the licensing impact.

Server generation and compatibility also matter

Two servers with similar core counts and memory capacity can differ significantly in performance, efficiency, management features and expansion capability because they belong to different generations.

When comparing used or refurbished equipment, also consider:

  • processor and platform generation;
  • memory type and speed;
  • PCI Express generation;
  • NVMe support;
  • RAID controller;
  • network interfaces;
  • iDRAC, iLO or another management tool;
  • operating-system and application compatibility;
  • future expansion capability.

New or used server?

Previous-generation Enterprise equipment can continue to serve many workloads very well, often at a significantly lower cost than a new platform.

The decision should consider not only age but also equipment condition, provenance, tests performed, parts availability, power consumption, performance, compatibility and expected service life.

At Rukam, equipment covered by the RUKAM Certified standard goes through the applicable selection, testing and preparation processes before being offered for sale.

Conclusion

Do not choose a server based only on the specification sheet.

CPU, memory and storage need to work in balance and according to the application. An oversized configuration can increase cost without providing a real benefit; an undersized configuration can compromise performance and expansion.

If you have questions about compatibility or sizing, Rukam's technical team can help evaluate the configuration best suited to your environment.

In Part 2: platform, redundancy, RAID, networking, expansion, remote management and other important points when choosing a server.