AMD's EPYC 8005 "Sorano" family has reshaped the mainstream single-socket server tier with a much bigger jump over its predecessor than UK buyers may expect. With seven SKUs spanning 8 to 84 cores on the same SP6 socket, procurement teams now need a sharper read on workload fit than a straight core-count comparison can give them.
View the data behind this chart
| 8025P (8 cores) | 48-core SKU | 8635P (84 cores) | |
|---|---|---|---|
| TDP per core | W12 | W4.1 | W2.7 |
Why Sorano matters for a UK refresh cycle
Sorano is AMD's Zen 5 refresh of the mainstream, single-socket EPYC 8004 "Siena" platform, and it brings a substantially larger jump in core counts, clockspeeds and memory support than the generation it replaces. For UK organisations running single-socket edge, branch or density-focused estates, this is the tier that typically gets evaluated alongside the bigger 2-socket EPYC 9005 line during a wider server refresh.
Because Sorano uses the same SP6 socket as Siena, some buyers will be able to treat this as a drop-in CPU upgrade on existing chassis, which materially changes the maths for a server configuration refresh versus a full platform swap. That said, several vendors are releasing new motherboards specifically for Sorano, so socket compatibility alone should not be assumed without checking the board revision.
A simplified SKU stack, with real trade-offs underneath
Unlike some AMD generations where features are gated by SKU tier, every Sorano chip — from the entry 8-core 8025P to the flagship 84-core 8635P — gets the same platform capability: six channels of DDR5 memory with 2DPC support, 96 PCIe Gen5 lanes, and full-size Zen 5 cores rather than the compact cores used in Siena. That consistency simplifies the buying decision down to three variables: core count, power envelope, and the knock-on effects for cache and memory bandwidth per core.
Every SKU also shares the same 4.5GHz maximum single-core turbo, so lightly threaded workloads have headroom regardless of which chip is chosen — though nobody specs an EPYC platform purely for single-thread performance.
Clock speed versus core count: where the sweet spot sits
All-core turbo clockspeeds fall roughly in line with core counts, but not perfectly. The 84-core 8635P tops out at 3.45GHz all-core, while the 24-core 8225P reaches 4.1GHz. The one exception is the 16-core 8125P, which despite having fewer cores than the 8225P actually posts a lower all-core turbo clock — a reminder that buyers should check the datasheet rather than assume a clean inverse relationship.
For workloads that need strong per-core performance without going to the very top of the range, the mid-tier 8325P has the strongest claim to being the sweet spot, balancing core count against clockspeed in a way the other SKUs don't quite match.
Power and efficiency: the per-core cost that changes TCO
Default TDPs scale directly with core count, but the efficiency picture is more interesting. The flagship 8635P draws 225W at default TDP for 84 cores — working out to just 2.7 watts per core, making it the most power-efficient SKU in the stack despite having the highest core count. By contrast, the 8-core 8025P sits at around 12 watts per core, since the same uncore and I/O die overhead is being amortised across far fewer cores.
This has a direct bearing on power and cooling budgets for UK data halls, particularly where rack density or energy costs are the binding constraint. Buyers consolidating several older single-socket boxes onto fewer, higher-core-count Sorano chips should model the per-core efficiency gain against the licensing and workload consolidation benefits — a calculation worth running alongside any VMware alternatives evaluation where licensing changes are already forcing a hardware rethink.
Cache and memory bandwidth: matching the chip to the workload
With AMD not shipping a 3D V-Cache server part in this generation, cache-per-core becomes a genuine differentiator between SKUs rather than a tiebreaker. The lower-core-count chips carry up to 8MB of L3 cache per core, while the 64-core 8535P — built from eight fully enabled CCDs — is the most cache-contested SKU at just 4MB per core. The flagship 8635P sits in between at 4.6MB per core across its 384MB total L3.
Memory bandwidth tells a similar story: the platform's 307GB/s of total bandwidth (from a shared six-channel DDR5-6400 controller) gives the 8-core 8025P an ample 38GB/s per core, dropping to just 3.7GB/s per core on the 84-core 8635P. Cache- and bandwidth-sensitive workloads — large in-memory databases, certain virtualisation profiles — should be profiled against this curve before committing to the highest core count on spec sheet appeal alone.
View the data behind this chart
| Core count | Clock profile | Cache per core | |
|---|---|---|---|
| 8025P – entry (8 cores) | 8 cores | Highest all-core clock in stack | 8MB per core |
| 8225P – 24-core | 24 cores | 4.1GHz all-core turbo | 5.3MB per core |
| 8325P – balanced pick | Mid-range core count | Strongest per-core balance | 8MB per core |
| 8635P – flagship (84 cores) | 84 cores | 3.45GHz all-core turbo | 4.6MB per core |
What this means for procurement decisions
The practical takeaway for UK buyers is that Sorano rewards workload profiling over raw core-count shopping. A density play for consolidated virtualisation favours the top-end 8635P for its efficiency and throughput; a cache- or bandwidth-sensitive workload may do better on one of the lower-core SKUs with 8MB per core; and the 8325P offers the best general-purpose balance of clock and core count.
Whichever tier fits, it's worth running the maths through an IT finance calculator to compare a Sorano-based refresh against extending the life of existing Siena or older single-socket estate, especially where ageing hardware is approaching a server end-of-life threshold. For teams specifying through major OEM channels, the Dell server configurator and HPE server configurator are the fastest way to see how Sorano SKUs land in real quoted builds, and our team is on hand via contact a Servnet engineer for workload-specific sizing.