Choosing a server processor is not simply a matter of finding the largest number of cores. The useful processor depends on what the server will actually do.
Practical example: small business virtualisation server
Choose the exact server only after balancing the workload and required resilience.
Scenario: A 35-user business wants one physical server for directory services, an accounting application, file services and three small virtual machines.
The design starts with the workload rather than a model number. Memory is budgeted for the hypervisor, each virtual machine and growth. Storage is separated into performance and capacity requirements. RAID is selected for availability, while a separate backup target is retained for recovery. Dual power supplies and multiple network interfaces are considered if the required server supports them.
Decision: The final server should be chosen only after checking processor capacity, DIMM population rules, drive bays and backplane, RAID controller, network interfaces, PSU configuration and the supported expansion path.
Common mistakes and selection checklist
Common mistakes
- Choosing a server from the processor model alone and treating memory, storage, networking and resilience as secondary details.
- Sizing only for today's workload and leaving no practical memory, drive or expansion path.
- Assuming RAID, redundant power supplies or virtualisation removes the need for a separate backup and recovery plan.
What happens if you get it wrong?
The server can be technically functional but still perform poorly, run out of expansion capacity early, or have a single failure that interrupts several business services at once.
Selection checklist
- List the workloads, users, applications and virtual machines the server must support.
- Check CPU sockets and cores, memory capacity and population rules, drive bays and backplane, RAID controller and network interfaces.
- Decide what must remain operational after a drive, PSU or network-path failure.
- Confirm backup, restore and recovery requirements separately from server redundancy.
- Check warranty, supported expansion and the expected three-to-five-year growth path.
Start with the workload
Different applications place different demands on processors. A basic file server can have very different requirements from a virtualisation host or a compute-intensive application.
Core count
More cores can allow a processor to handle more concurrent work, but the benefit depends on whether the workload can use the available processing capacity effectively.
Single-thread and multi-thread workloads
Some applications benefit strongly from additional parallel processing, while others may depend more heavily on the performance of individual processing threads. The application should therefore influence processor selection.
Memory and I/O matter too
A powerful processor cannot compensate for insufficient memory or unsuitable storage and network infrastructure. Server performance is a system-level consideration.
Virtualisation
Virtualisation consolidates multiple workloads onto one physical server. Processor selection should account for the number and type of virtual machines, their expected utilisation and future growth.
Platform compatibility
The processor must be supported by the chosen server platform. Socket, chipset, firmware, cooling, memory architecture and platform generation all matter when selecting a compatible configuration.
Avoid specification chasing
A higher specification is not automatically the correct choice. If the workload does not benefit from the additional capability, the extra capacity may not provide a meaningful improvement.
- What applications will run?
- Are workloads single-threaded, multi-threaded or mixed?
- How many virtual machines are planned?
- What memory capacity accompanies the processor?
- What storage and network performance is required?
- Is the processor supported by the selected server platform?
- What future workload growth is expected?
Confirm the exact product specification, supported configuration and compatibility before ordering. Platform generation, firmware, licences and optional components can change what a product supports.