Stranded DRAM at fleet scale: why half your server memory sits idle

Memory is stranded when it is installed in a server, powered, and paid for, but cannot be used by any workload that needs it — because it is physically bolted to a CPU (or a VM) that happens not to need it right now. It is not broken and it is not free; it is simply unreachable by the job one rack over that is short on memory. Multiply that across thousands of servers and a large fraction of a fleet's most expensive component is doing nothing.

Stranding is not a procurement mistake; it falls out of how servers are sized. You buy each machine with enough DRAM for its peak — the worst-case working set — because a job that runs out of memory fails, and you cannot add DRAM to a running server. But workloads rarely sit at peak. The gap between peak-provisioned and average-used is idle by construction, and it exists on every machine at once.

Two forces widen the gap:

• Fixed ratios. Servers ship with a fixed DRAM-per-core ratio chosen for the hungriest tenant, so memory-light workloads over-provision massively.
• Isolation. In a virtualized fleet, memory rented to one VM cannot be lent to another even when idle — it is stranded inside the rental boundary.

This is measured, not hand-waved. Microsoft Azure's Pond study (ASPLOS 2023) instrumented production cloud traces and found:

• 50% of VMs never touch 50% of the memory they rent — that memory is stranded inside the rental.
• Up to about 25% of total DRAM is stranded at any given moment.
• DRAM is more than 50% of server cost — so stranded memory is stranded capital, not a rounding error.
• Pooling across just 8–16 CPU sockets captures most of the achievable benefit; you do not need a giant pool.

Industry restatements land in the same band: most enterprise DRAM sits locked to CPUs at roughly 50–60% utilization. The precise number varies by fleet and workload; the direction does not.

Stranded DRAM was always wasteful, but two things turned it from a footnote into a capital problem:

• Memory prices surged. DRAM and HBM prices rose sharply through 2025 in the AI memory supercycle, with high-bandwidth memory effectively sold out into 2026. Idle memory you already own is worth more, and replacing it costs more.
• AI made memory the dominant line. As the GPU memory wall pushes teams to buy capacity they do not compute against, the share of spend going to memory rises — and so does the absolute cost of leaving it stranded.

Put together: a fleet is paying premium prices for its most expensive component and using a fraction of it. That is the economic case for changing how memory is attached to servers.

The fix mirrors the GPU-side answer: disaggregate the memory. Instead of each server owning a fixed, over-provisioned DRAM allotment, capacity moves into a shared pool that many servers draw from on demand. Idle memory in one place serves a shortfall in another, so the fleet is sized closer to its aggregate need rather than the sum of every server's individual peak — which is where the stranding lived.

Two fabrics carry the pool, and their status differs (the full comparison is in the hub): CXL memory pooling is the low-latency, load/store approach, real and advancing, but multi-host pooling across servers is still maturing toward fleet-scale deployment. RDMA / RoCEv2 disaggregation is a pool of DDR5 shared to many servers over standard lossless Ethernet, deployable today with the network you already run.

For a fleet that wants to reclaim stranded DRAM now, the Ethernet-based pool is the deployable path. A disaggregated-memory appliance — a rack of high-capacity DDR5 shared over RDMA/RoCEv2 — lets servers expand memory capacity and utilization without over-provisioning DRAM per server, which is precisely the stranding it is meant to end. The TORmem M1000 is that appliance: powered by AMD EPYC and high-capacity DDR5, serving a shared pool to multiple servers over RDMA over RoCEv2 so remote memory behaves close to local. It rides a low-latency Ethernet fabric of the kind built from the TORswitch and pluggable optics.

If your utilization dashboards show memory provisioned but idle across the fleet, tell us the server shapes, the workloads, and the fabric you run — we can help plan a pooled-memory configuration and source the appliance. Start with the GPU memory wall, or browse the hardware overview.