{
  "slug": "semeru",
  "term": "Semeru",
  "aliases": [
    "Semeru distributed JVM"
  ],
  "definition": "Semeru is a research JVM that coordinates remote heap paging and garbage collection across a CPU server and memory servers.",
  "note": "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. [paper]\n\nCollection 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. [paper]\n\nLocal 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. [readme]\n\nVersion 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. [readme] [header]\n\nEvaluation: 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. [paper]\n\nTerminology: Collection here concerns object reachability, not NAND erase-block reclamation. Remote DRAM and a swap interface alone do not establish crash durability. [paper]",
  "status": "research",
  "advantages": [],
  "limitations": [],
  "related": [
    "aifm",
    "fastswap"
  ],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-11-15",
  "citations": [
    {
      "id": "paper",
      "title": "Wang et al. Semeru: A Memory-Disaggregated Managed Runtime. OSDI 2020, pp. 261-280; sections 3-6.",
      "url": "https://www.usenix.org/system/files/osdi20-wang.pdf",
      "accessed": "2026-11-15"
    },
    {
      "id": "readme",
      "title": "Semeru authors: setup, FAQ and known issues, pinned revision 829512c",
      "url": "https://github.com/uclasystem/Semeru/blob/829512c670036de778d4a1167b2a3ca3b2b566b3/README.md",
      "accessed": "2026-11-15"
    },
    {
      "id": "header",
      "title": "Semeru authors: RDMA region geometry and byte-unit constants, pinned revision 829512c",
      "url": "https://github.com/uclasystem/Semeru/blob/829512c670036de778d4a1167b2a3ca3b2b566b3/linux-4.11-rc8/include/linux/swap_global_struct.h",
      "accessed": "2026-11-15"
    }
  ],
  "provenance": [
    "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."
  ]
}
