pond · research · also Pond memory pooling

Pond

Pond is a research CXL memory-pooling design that assigns local and pooled DRAM to virtual machines using predicted latency sensitivity and untouched memory.

Pond preallocates a VM's memory rather than oversubscribing it. A memory-only virtual NUMA node (zNUMA) steers initial guest allocations toward local DRAM. Predictions choose the split; a QoS monitor mitigates mistakes. Each pool slice belongs to at most one host at a time. [1]

Evidence: Experiments cover 158 workloads using NUMA-based CXL emulation. Simulations use 75 days of requests from 100 clusters in 34 datacenters. Figure 21 reports 7% lower aggregate DRAM requirements for a 16-socket pool in the higher-latency scenario, at a 5% performance-degradation margin and 98% target tail percentage. This is a trace-driven simulation result, not a measured fleet saving. [1]

Latency denominator: local/remote pairs are 78/142 ns and 115/255 ns. Remote latency is about 1.82x and 2.22x local latency, or 82% and 122% higher. The paper's 182%/222% labels describe ratios, not additional increases of those amounts. They are not application slowdown. [1] [4]

Pooling scope: CXL 2.0 excludes mapping one physical memory location to multiple hosts simultaneously. Logical devices can share bandwidth without sharing the same bytes. This is version-specific, not a restriction on every later CXL version. [3]

Capacity check: aggregate free bytes do not ensure VM admission. Constructed examples separate free cores, local GiB, accessible pool GiB and an assumed minimum-local requirement; they do not predict that requirement from performance. [4] [5]

Relations

related
CXL memory expansion, Memory stranding, CXL memory pooling

Limitations

  • The author artifact supplies emulation scripts, not the full Pond system. Its README warns against using memeater for memory-tiering tests because its pages can migrate. [2]

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. Pond author artifact README, commit 5ac0e66b3624b9324cc9042abcd930127005d4bc: emulation scope and memory-tiering warning (accessed 2026-11-16)
  3. CXL Consortium: CXL 2.0 memory pooling Q&A, 21 May 2021; ownership and bandwidth (accessed 2026-11-16)
  4. Hesela: constructed single-VM admission examples and latency-ratio arithmetic (JSON) (accessed 2026-11-16)
  5. Hesela: executable admission predicate and latency arithmetic (JavaScript) (accessed 2026-11-16)
Sources & caveats
  • Primary-source review of the ASPLOS 2023 paper (CC BY 4.0), version-pinned author artifact and CXL Consortium explanation. No native Pond or CXL workload experiment was run by Hesela.
  • The worked admission predicate is an original constructed example, not the Pond scheduler, trace replay, performance model or cost forecast. It excludes contention, topology, fragmentation, failure domains and reconfiguration delays.
  • The pinned scripts disable remote CPUs and change host settings, including swap and ASLR. They were inspected, not executed. Reproduction requires an isolated, appropriately authorized system. [2]

JSON: /data/terms/pond.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Pond. Hesela. 2026-11-16. https://hesela.dev/terms/pond/