semeru · research · also Semeru distributed JVM

Semeru

Semeru is a research JVM that coordinates remote heap paging and garbage collection across a CPU server and memory servers.

Mechanism: A universal Java heap preserves each object's virtual address across its CPU and hosting memory server. Application threads run on the CPU server; memory servers execute collection tasks near the data. [1]

Collection boundary: Memory servers trace mostly evicted regions concurrently. Evacuation and pointer repair still require a coordinated stop-the-world phase; cached regions are traced on the CPU server. Unreachable cycles spanning regions require full-heap collection. [1]

Local capacity: Moving Java heap pages remotely does not make native memory unlimited. The pinned prototype warns that native-memory pressure can cause OOM and requests local metadata headroom. It supports one application JVM per CPU server. [2]

Version scope: The public setup targets a modified Linux 4.11-rc8 and OpenJDK 12.0.2. Its header defines eight 4 GiB data regions: 32 GiB, separately from a 4 GiB metadata region. RDMA regions and GC heap regions have different sizes. [2] [3]

Evaluation: Eight Spark/Flink programs ran on one CPU server and three memory servers. Reported gains compare specified swap configurations; the fully local G1 execution is a separate baseline. This does not establish faster-than-local-memory execution. [1]

Terminology: Collection here concerns object reachability, not NAND erase-block reclamation. Remote DRAM and a swap interface alone do not establish crash durability. [1]

Relations

related
AIFM, Fastswap

Citations

  1. Wang et al. Semeru: A Memory-Disaggregated Managed Runtime. OSDI 2020, pp. 261-280; sections 3-6. (accessed 2026-11-15)
  2. Semeru authors: setup, FAQ and known issues, pinned revision 829512c (accessed 2026-11-15)
  3. Semeru authors: RDMA region geometry and byte-unit constants, pinned revision 829512c (accessed 2026-11-15)
Sources & caveats
  • Primary-source synthesis and static inspection of pinned configuration constants; no Semeru installation, RDMA benchmark, crash experiment or reproduction of the paper's performance results.
  • The paper evaluates three memory servers; the pinned header defaults to two. The source snapshot is not asserted to be the exact configuration used for the published measurements.
  • GiB values follow ONE_GB = 1073741824 in the pinned header. Metadata address-space reservation is not a measurement of resident memory or application headroom.
  • The durability qualification is an interpretation of the described volatile-memory architecture, not a tested failure-recovery guarantee.

JSON: /data/terms/semeru.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Semeru. Hesela. 2026-11-15. https://hesela.dev/terms/semeru/