Clover
Clover is a research key-value store that separates direct access to passive disaggregated persistent memory from metadata management on dedicated servers.
In the ATC 2020 design, new values are written out of place, then linked into a version chain with RDMA compare-and-swap. Cached cursors and asynchronous shortcuts reduce traversal; a shortcut need not identify the newest version. Metadata servers allocate space and reclaim versions. [1]
The evaluation used DRAM as PM and ordinary RDMA writes as a stand-in for durable writes. Its performance results are not measurements of persistence on real PM hardware. [1] Remote persistence also depends on the protected components, DDIO and operation ordering, not simply an RDMA completion. [2]
The pinned tutorial separates metadata, compute and memory-node roles, with memcached distributing RDMA connection metadata. The benchmark replays pre-generated YCSB traces rather than invoking YCSB directly. [3]
Relations
Limitations
- Single-entry atomicity is not a multi-key transaction guarantee; write contention can add chain walks and retries. [1]
Citations
- Tsai, Shan and Zhang. Disaggregating Persistent Memory and Controlling Them Remotely. USENIX ATC 2020, sections 3-6, pp. 33-48.
- Sanidhya Kashyap, Dai Qin, Steve Byan, Virendra J. Marathe and Sanketh Nalli. Correct, Fast Remote Persistence. arXiv:1909.02092v1, sections 2-3.
- WukLab pDPM: Clover tutorial, roles and trace-based YCSB setup; commit 5c68507ef617d297727aa9e26a7ee60d0b1901e7.
Sources & caveats
- Primary-paper and pinned-author-code review. No Clover deployment, power-failure test or performance reproduction was performed.