foedus · research · also Fast Optimistic Engine for Data Unification Services

FOEDUS

FOEDUS is a transactional storage engine that pairs mutable DRAM pages with immutable snapshot pages constructed from logical logs.

Dual pages: A snapshot can lag behind its volatile counterpart. A serializable reader following a snapshot because no volatile page exists records that pointer and validates its continued absence at precommit. Immutable contents alone do not settle concurrent visibility. [1]

Snapshots: The log gleaner constructs changed pages and reuses unchanged descendants from older snapshots. It does not copy the live DRAM tree or require readers to merge every historical snapshot. Its progress still limits how much volatile state can be reclaimed. [1]

Acknowledgement: Successful precommit_xct returns a commit epoch, not a durability confirmation. Clients can continue processing while withholding results, or use wait_for_commit. The relevant threshold is the durable global epoch, not simply the current epoch. [2]

Read-only results: The log API explicitly requires both read-only and read-write transactions to await that threshold before returning results. A negative wait duration means unbounded waiting; zero polls without blocking; a timed wait may report timeout instead of success. A timeout must not be presented as durable acknowledgement. [3]

Relations

related
Silo, Non-volatile random-access memory

Limitations

  • The 2015 evaluation reached 240 physical cores, not 1,000; its NVRAM experiments used DRAM-backed tmpfs with injected I/O delays, not physical NVRAM devices. [1]
  • The library assumes fsync reaches durable storage through the filesystem and device stack; its ACID guarantee depends on that assumption. [4]

Citations

  1. Kimura. FOEDUS: OLTP Engine for a Thousand Cores and NVRAM. SIGMOD 2015, pp. 691-706; sections 4, 6-7, 9. DOI: 10.1145/2723372.2746480. (accessed 2026-11-15)
  2. HewlettPackard/foedus_code c40ecfcb8d2b: XctManager precommit_xct and wait_for_commit contracts. (accessed 2026-11-15)
  3. HewlettPackard/foedus_code c40ecfcb8d2b: LogManager durable epoch and wait_until_durable contract. (accessed 2026-11-15)
  4. HewlettPackard/foedus_code c40ecfcb8d2b: core library requirements and fsync assumption. (accessed 2026-11-15)
Sources & caveats
  • Source synthesis of the 2015 paper and later implementation documentation pinned to c40ecfcb8d2b2441b17807109848b966c0ad7e45; no native execution, benchmark reproduction or power-loss test.
  • The paper and pinned code are different versions. The record does not certify current-platform compatibility or production readiness.

JSON: /data/terms/foedus.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

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