Kubernetes says fast NVMe-backed node swap can raise pod density by as much as 3× for some memory-heavy workloads.

In an October 5 benchmark, the project tested CI/CD kernel builds, browser sandboxes and isolated Python runtimes. Kubernetes reports that dormant memory could be paged from RAM to fast local SSDs, letting one node run up to 240 isolated Python sandboxes in its test.

KubeCon NA 2025 — Kubernetes swap feature lead Itamar Holder explains production swap tuning and memory-pressure behavior.

The feature reached General Availability in Kubernetes v1.34. The project’s current swap documentation still warns that slow storage, noisy neighbors and swap-unaware scheduling can create performance problems. Fast NVMe matters because paging to slow disks can be dramatically more expensive.

This builds directly on concepts in BitcoinVersus.Tech’s virtual-memory explainer, our NVMe vs. SATA guide, and load-balancer overview for broader cluster infrastructure context.

r/kubernetes — operators discuss swap, zswap and fast local NVMe for bursty memory workloads.

Bottom line: Kubernetes is no longer treating swap as something operators must simply disable. For bursty or idle-heavy workloads—especially agent sandboxes—fast local storage can act as a second memory tier, but it still needs careful tuning.

Editor’s Note

The 3× figure comes from specific Kubernetes benchmark workloads and should not be treated as a universal production result.

Follow BitcoinVersus.Tech on LinkedIn. Support independent research: 3C9o19EH5HSiwEPyCTmEKzxhNCbo2X6TTb.

BitcoinVersus.Tech is not a financial advisor. Content is provided for informational purposes.