The default server purchase is a dual-socket box, and for a great many workloads that default now costs more than it should. The Dell PowerEdge R670 is a single-socket 1U built on Xeon 6, and modern single sockets carry enough cores, memory channels and PCIe lanes that one CPU does the work two used to. For edge sites, licence-bound roles and dense single-socket hosting, the R670 sheds the cost of a second CPU and its licences without giving up the capability the workload actually needs. This guide covers when one socket beats two, and how to spec the R670 well.
Why single-socket is back
For years a serious server meant two sockets, because one CPU could not provide enough cores, memory or I/O. That has changed. A single current-generation Xeon 6 now offers a high core count, a full set of memory channels and a generous allocation of PCIe Gen5 lanes, enough that for many workloads a single-socket server is not a compromise but the right-sized answer.
The R670 is Dell's expression of that shift: a single-socket 1U on the Xeon 6 platform, aimed at roles that do not need the cores or memory of a dual-socket box and would rather not pay for them. Removing the second CPU removes not just silicon cost but a chunk of per-core licensing and some power, which is exactly where single-socket value comes from.
The licensing argument
The strongest case for single-socket is often licensing. Hypervisor and many guest licences are per-core with a per-CPU minimum, so a second socket can drag in a block of cores you must licence whether or not you use them. For a workload that fits comfortably on one CPU, a single-socket server avoids that floor and can materially lower recurring cost over the life of the box.
This is the same licence-aware logic that argues for fewer-faster cores on any host, taken one step further: not just the right number of cores, but the right number of sockets. We weigh the silicon and licence cost together when sizing, because on a licence-bound workload the socket count can matter more to total cost than the CPU model, a theme in how to spec a server in 2026.
- •One Xeon 6 now provides the cores, memory channels and Gen5 lanes many workloads need
- •A second socket can force a per-CPU licence minimum you pay for but do not use
- •Single-socket lowers silicon, licence and power cost where the workload fits one CPU
- •Decide socket count from the workload and the licences, not from habit
Edge and core roles that fit
The R670 suits two broad families of work. The first is edge and remote-site roles: a 1U single-socket box is the right size for a branch, a retail location or a remote core function where you need real server capability but not a dual-socket footprint, and where power and space are constrained. Its modest, self-contained nature is a feature in these settings.
The second is licence-bound and dense single-socket hosting: domain controllers and other lightweight infrastructure roles, single-socket virtualisation hosts, and dense hosting where many right-sized single-socket nodes beat fewer oversized ones. For the deliberately anti-over-spec roles such as a domain controller, the R670 is a natural fit alongside the guidance in specifying a domain controller.
Speccing the R670
Even on one socket the fundamentals hold. Size cores from the workload and the licences rather than maxing them out, populate the memory channels in a balanced map so the single CPU gets full bandwidth, and remember that one socket means one set of channels, so the population map is if anything more important to get right. The Xeon 6 single-socket platform still benefits from EDSFF NVMe and PCIe Gen5 where the workload uses them.
Storage and resilience follow the usual rules: a thin NVMe footprint for local needs with capacity on shared storage where appropriate, boot on a separate mirrored BOSS device, and the production baseline of dual power, redundant fans and iDRAC out-of-band management. A single-socket server is smaller, not less serious, and a production R670 deserves the same resilience as any other host.
When you still want two sockets
Single-socket is the right-sized answer for many roles, but not all. If a workload needs more cores or memory than one CPU can provide, or more PCIe lanes than a single socket exposes for many GPUs or HBAs, the dual-socket R660 is the correct choice and forcing the work onto one socket would compromise it. The R670 is for workloads that genuinely fit one CPU, not a way to under-spec a demanding one.
Memory-bound workloads that want the bandwidth of two CPUs' worth of channels, dense consolidation that needs the cores of two sockets, and anything that will grow past a single CPU's envelope all belong on the R660 or larger. The skill is matching socket count to the workload honestly, which is exactly the single-versus-dual decision we cover in single-socket vs dual-socket servers.
Putting it together
Reach for the R670 when one socket genuinely fits the workload and the licence saving is real: edge sites, licence-bound roles and dense single-socket hosting, specced with balanced memory, mirrored boot and full resilience. Build the configuration and request a quote in our Dell server configurator. For the wider socket-count decision read single vs dual socket, and see the range on our Dell servers hub.