Buying guide · Performance optimization · Server hardware

When a Gen9 Server Is Still the Smart Buy

· 5 min read · Server Depot

When a Gen9 Server Is Still the Smart Buy

ProLiant Gen9 is the HPE generation built around Intel Xeon E5-2600 v3 (Haswell-EP) and v4 (Broadwell-EP) processors on the LGA 2011-3 socket: DDR4 across four memory channels per socket, PCIe 3.0 throughout, and iLO 4 for out-of-band management. It is not current hardware, and nobody should pretend otherwise. It is still the correct answer for a specific and reasonably large set of jobs, and the deciding factor is rarely raw performance — it is the licensing model sitting on top and the I/O profile of the workload underneath.

What a Gen9 server actually is

Three chassis cover most of what people mean when they say Gen9:

Model Form factor Sockets DIMM slots Front drive bays
ProLiant DL360 Gen9 1U rack 2 24 8 or 10 SFF, or 4 LFF
ProLiant DL380 Gen9 2U rack 2 24 Up to 24 SFF, or 12 LFF
ProLiant DL560 Gen9 2U rack 4 (E5-4600 v3/v4) 48 Up to 8 SFF

A two-socket Gen9 tops out at 22 cores per socket with the E5-2699 v4 at 145 W TDP — 44 cores and 88 threads in one node. Further down the stack sit parts such as the 14-core E5-2680 v4 at 120 W and the 12-core E5-2650 v4 at 105 W, which carry a lighter thermal and power load than the top bin. Each socket exposes 40 PCIe 3.0 lanes, so a populated dual-socket board has 80 lanes to spread across the risers, the embedded Smart Array controller, and the FlexibleLOM network card.

Memory is where the platform still earns its rack space. Twenty-four DIMM slots on a two-socket board is twelve per socket: four channels, three DIMMs deep. Broadwell-EP runs DDR4 at up to 2400 MT/s on the processor SKUs rated for it, where Haswell-EP stops at 2133, which is roughly 76.8 GB/s of theoretical bandwidth per socket with all four channels filled. Entry-level v3 and v4 parts are rated lower than the platform maximum, so read the processor's own memory specification rather than assuming. Populating the third DIMM on every channel forces the memory clock down, so two DIMMs per channel — sixteen modules in a dual-socket box — is the configuration to aim for. Sixteen 32 GB RDIMMs gives 512 GB without reaching for an unusual part.

Two rules catch people out: v3 and v4 processors cannot be mixed in the same server, and a v4 chip needs a system ROM new enough to recognize it. Buy the pair together and check the ROM level before the processors arrive.

The jobs Gen9 still does well

  • Backup and archive targets. A 12-bay LFF DL380 Gen9 fronting a Veeam repository or a ZFS dataset is limited by spindles and network ports, not by instructions per clock.
  • Labs, staging, and build agents. Compilers and integration tests do not care which Xeon generation is underneath, and 88 threads goes a long way in a CI pool.
  • Memory-heavy, CPU-light services. Caches, search indexes, and development copies of production databases. Twenty-four DDR4 slots and widely available registered modules are the entire argument.
  • File, media, and video surveillance storage. Sustained sequential throughput scales with disks and controller lanes, both of which Gen9 has.
  • Open-source virtualization and storage. Proxmox VE, XCP-ng, TrueNAS, Ceph. When the stack is not licensed per core, core count becomes a capacity decision instead of a billing one.
  • Fleet spares. If you already run Gen9, another identical node means one firmware baseline, one driver set, one spares kit.

Where the platform runs out

Per-core licensing is the first wall. Windows Server is licensed with a minimum of eight cores per processor and sixteen per server, and current VMware subscription licensing bills a minimum of sixteen cores per populated CPU. A two-socket Gen9 with two 10-core processors is licensed as 32 cores while delivering 20 — you are licensing capacity the silicon does not have. When the software on top charges per core, denser and newer processors usually win that arithmetic before performance enters the discussion.

The remaining limits are architectural. Broadwell-EP has AVX2 but no AVX-512 and no VNNI, so modern inference and HPC libraries lose their fast path. NVMe on Gen9 exists only through optional express-bay kits and never approaches later densities. HPE has required entitlement — an active warranty or support agreement — to download firmware and Service Pack for ProLiant bundles for several years, so decide how you will obtain firmware before you need it at two in the morning. Check your hypervisor's supported-processor list as well: Haswell- and Broadwell-era Xeons sit near the boundary of what current releases still certify, and that boundary keeps moving.

  Gen9 Gen10
Processor family Xeon E5-2600 v3 / v4 Xeon Scalable 1st / 2nd gen
Socket LGA 2011-3 LGA 3647
Memory channels per socket 4 6
DIMM slots (dual socket) 24 24
Peak memory speed 2400 MT/s 2666 / 2933 MT/s
PCIe generation 3.0 3.0
Vector extensions AVX2 AVX-512
Management iLO 4 iLO 5

A short pre-purchase checklist

  • Decide v3 or v4, and never mix them in one chassis. Confirm the system ROM supports the processors you are buying.
  • Aim for two DIMMs per channel. Sixteen matched modules in a dual-socket box beats twenty-four mismatched ones.
  • Smart Array P440ar for hardware RAID; the H240ar host bus adapter if ZFS, Ceph, or Storage Spaces is going on top — those stacks want raw disks and unfiltered SMART data.
  • iLO Advanced is a licensed feature. Remote console and virtual media are not included in base iLO 4.
  • Rear drive cages and express bays consume riser slots, so decide drives and PCIe cards in the same conversation. The common Flex Slot power supply options are 500 W, 800 W, and 1400 W; size for CPU TDP plus fully populated DIMMs plus drives, and make sure both units match.

Where to go from here

If the workload is bounded by disks, memory capacity, or network ports rather than per-core throughput, Gen9 remains a rational purchase. Look through the available HPE ProLiant Gen9 servers to see which chassis and drive layouts are on hand. If what you need is a specific combination — a particular processor pair, DIMM population, controller, and bay count — put it together on the build your server page and send the configuration in for a quote. If the licensing math points toward a newer platform, say so in the request and we will spec that instead.