{
  "slug": "aifm",
  "term": "AIFM",
  "aliases": [
    "Application-Integrated Far Memory"
  ],
  "definition": "AIFM is a research runtime that uses application-aware pointers and containers to move objects between local and remote memory.",
  "note": "Mechanism: C++ interfaces expose object access patterns to a runtime using TCP-connected memory. Data structures can guide prefetching, eviction and remote computation instead of relying only on page faults. [paper]\n\nPointer lifetime: A DerefScope fences evacuation while local data is in use. Accessing a raw pointer obtained by dereferencing outside that scope is undefined behavior; the remotable pointer can remain alive after its object moves. [paper]\n\nPrototype limits: The pinned implementation permits only one live DerefScope per thread. Remote-space garbage collection is not implemented; its exhaustion handler only prints a warning. Local-memory reclamation does exist. [readme] [manager]\n\nDeployment scope: The paper's prototype connects each compute server to one memory server, without cross-client sharing or runtime resizing. Its SSD backend has block-size amplification and cannot run the remote computations supported by the memory backend. [paper]\n\nPerformance interpretation: The evaluation uses two 25 Gbit/s machines and workload-specific local-memory budgets. Local-hit overhead, remote access and end-to-end throughput are different measurements; none establishes universal local-RAM speed. [paper]\n\nLater comparison: Eden's authors identify object-access instrumentation and application changes as AIFM trade-offs. Their hybrid approach uses hints at selected code locations and hardware page faults elsewhere. This comparison concerns integration and access costs, not crash durability. [eden]",
  "status": "research",
  "advantages": [],
  "limitations": [],
  "related": [
    "infiniswap",
    "carbink",
    "fastswap",
    "eden",
    "semeru",
    "dilos"
  ],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-11-15",
  "citations": [
    {
      "id": "paper",
      "title": "Ruan, Schwarzkopf, Aguilera and Belay. AIFM. OSDI 2020, pp. 315-332; sections 4.2.2, 7 and 8.",
      "url": "https://pdos.csail.mit.edu/papers/aifm:osdi20.pdf",
      "accessed": "2026-11-15"
    },
    {
      "id": "readme",
      "title": "AIFM authors: README, supported platform and known limitations, pinned revision",
      "url": "https://github.com/AIFM-sys/AIFM/blob/fa4f31ce827501ad52f5a5ca9249ef04ba92b467/README.md",
      "accessed": "2026-11-15"
    },
    {
      "id": "manager",
      "title": "AIFM authors: FarMemManager remote allocation and unimplemented far-memory GC, pinned revision",
      "url": "https://github.com/AIFM-sys/AIFM/blob/fa4f31ce827501ad52f5a5ca9249ef04ba92b467/aifm/src/manager.cpp",
      "accessed": "2026-11-15"
    },
    {
      "id": "eden",
      "title": "Yelam et al. A Developer-friendly approach to Application-integrated Far memory. USENIX ;login:, March 2025.",
      "url": "https://www.usenix.org/publications/loginonline/developer-friendly-approach-application-integrated-far-memory",
      "accessed": "2026-11-15"
    }
  ],
  "provenance": [
    "Primary-source synthesis, not an AIFM execution, performance replication or crash-recovery experiment.",
    "The paper and pinned source describe a research prototype. Later comparisons use their own workloads and should not be pooled as one benchmark."
  ]
}
