Rack servers: Intel Xeon and AMD EPYC

A rack server is a chassis sized in rack units that carries the processors, memory, drives and network adapters for one workload. Most decisions come down to how many U you can spend, how many drives you need in front and whether the workload is core-hungry or clock-hungry. We supply 1U, 2U and 4U rack servers with current-generation Intel Xeon and AMD EPYC, tower units, and GPU and high-density nodes for AI and HPC.

Product families we supply

Product familyBrandCapacity / formatProduct page
FusionServer (xFusion) rackHuawei1U/2U/4U rack
FusionServer GPU / yüksek yoğunlukHuaweiGPU and high-density nodes
PowerEdge R serisi (Intel)Dell1U/2U/4U rack, 4th/5th gen XeonView product
PowerEdge R serisi (AMD)DellEPYC Genoa/Bergamo
PowerEdge GPU / AIDellAI and HPC
ProLiant DL Gen11 (Intel)HPE1U/2U/4U rackView product
ProLiant DL Gen11 (AMD)HPEEPYC
Alletra Server / ApolloHPEAI and HPC
ThinkSystem SR (Intel)Lenovo1U/2U/4U; 4th/5th gen XeonView product
ThinkSystem SR (AMD)LenovoEPYC
ThinkSystem ST (tower)Lenovotower format
ThinkAgile / ThinkSystem DM-DE (depolama)LenovoHCI and storage
Hyper SuperServer (X13, Intel)Supermicro1U/2U, 4th/5th gen Xeon
Ultra / CloudDC (X13)Supermicro1U/2U, high I/O
A+ Server (H13/H14, AMD)SupermicroEPYC 9004/9005
GPU SuperServerSupermicroAI / GPU
SuperStorageSupermicrohigh-density storage server

Product families we actually source. Capacities are the manufacturer’s stated series ranges, not a quotation. Exact order codes depend on voltage, outlet type, battery configuration and region and are confirmed on the quote.

Which one should you choose?

1U, 2U or 4U?

1U maximises servers per rack and constrains you to low-profile cards and small coolers. 2U is the practical default: more drive bays, full-height cards, quieter and cooler fans. 4U is for GPU nodes and drive-heavy builds where airflow and card length decide the chassis, not the density.

Intel Xeon or AMD EPYC?

EPYC generally offers more cores and more memory channels per socket, which suits virtualisation density and throughput workloads. Xeon still leads on certain accelerated and per-core-licensed workloads. If your software is licensed per core, the cheaper server can easily be the more expensive decision. Check the licence model before the CPU.

How many drive bays, and what type?

Front bay count fixes what the chassis can ever become. NVMe needs direct PCIe lanes and a backplane that supports it; adding NVMe later to a SAS-only backplane is not a field upgrade. Decide the bay count and the interface at purchase, and leave the capacity to be filled over time.

Memory, and how it is populated

Populating every channel matters more than the total figure. A half-populated board loses bandwidth no capacity upgrade recovers. Tell us the target capacity and we configure the DIMM layout to fill channels evenly rather than reaching the number the cheapest way.

Do you need GPUs?

GPU nodes change the power and cooling conversation entirely: one dense node can draw more than a whole rack of general-purpose servers. If GPUs are in scope, the rack, the PDU and the containment need quoting at the same time, or the servers arrive and cannot be switched on.

Warranty and on-site response

For a production server the response time matters more than the box. Next-business-day is fine for a clustered workload; a standalone server carrying the business wants 4-hour on-site. Availability of that service level varies by country: tell us the delivery country and we confirm what is actually offered there.

Request a quote

Tell us the workload, the core and memory target, drive count and delivery country. If GPUs are involved, mention it: the rack and PDU get quoted with the servers.

Request a Quote (EN)