memory-stranding · shipping

Memory stranding

Memory stranding is available memory capacity that cannot be allocated to an otherwise relevant workload because another placement resource or constraint is exhausted.

In Pond's motivating case, a server has unallocated DRAM after its CPU cores have been allocated. This differs from untouched memory inside an already provisioned VM: one concerns placement capacity, the other concerns access to assigned capacity. [1]

Constructed example: host A has 0 free cores and 64 GiB local memory; host B has 8 free cores and 16 GiB local memory. A new VM needs 4 cores and 32 GiB. No host can admit it without pooling, even though 80 GiB is free in total. In a second configuration, moving 16 GiB of A's unallocated capacity to an accessible pool lets B use 16 GiB local plus 16 GiB pooled memory. Total free capacity remains 80 GiB; it has not been created by pooling. [2]

Local-memory constraint: if that VM requires at least 24 GiB local memory, B cannot admit it even with the 16 GiB pool. The minimum-local requirement is an input assumption, not a measured latency guarantee. The executable predicate tests one VM against a static snapshot, with integer GiB capacity and no oversubscription. [2] [3]

Engineering implication: record which resources are free, which host can access them and which workload constraints apply. Summing free bytes across hosts is insufficient evidence of allocatable capacity; neither an idle-page count nor a pool's name supplies the missing placement contract.

Relations

related
Pond, CXL memory expansion, CXL memory pooling

Citations

  1. Li et al. Pond: CXL-Based Memory Pooling Systems for Cloud Platforms. ASPLOS 2023, pp. 574-587. DOI 10.1145/3575693.3578835; sections 2-6. (accessed 2026-11-16)
  2. Hesela: constructed single-VM admission examples and latency-ratio arithmetic (JSON) (accessed 2026-11-16)
  3. Hesela: executable admission predicate and latency arithmetic (JavaScript) (accessed 2026-11-16)
Sources & caveats
  • The definition follows the resource-stranding distinction in Pond; the capacity examples are explicitly constructed by Hesela, not observations of Azure or a hardware experiment.
  • Shipping here classifies an established systems concept; it does not claim that Pond is a shipping product.

JSON: /data/terms/memory-stranding.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Memory stranding. Hesela. 2026-11-16. https://hesela.dev/terms/memory-stranding/