Motor: Enabling Multi-Versioning for Distributed Transactions on Disaggregated Memory
Talkat 18th USENIX Symposium on Operating Systems Design and Implementation (OSDI '24) · 2024-07-10..07-12·
summary
Motor enables multi-version distributed transactions on disaggregated memory by storing version metadata contiguously so a coordinator finds the right version with single network RTT to fetch versions and then reads values via one-sided RDMA MVCC. A consecutive version tuple (CVT) packs headers and per-version attribute deltas, uses preemptive overwrite GC plus anchor checks to avoid corruption, eliminates remote logging, and on a 3-memory-node RDMA testbed yields up to 98.1% throughput gain and millisecond recovery.
AI-written summary · about
chapters (12)
- 0:00Motor introduction
- 1:07Disaggregated memory & transactions
- 2:55Single versioning limits
- 4:00Multi-versioning advantages
- 5:03Motor’s version tree
- 6:49Memory overhead & GC
- 8:13RDMA-based MVCC protocol
- 10:44Transaction execution
- 11:27Experimental setup
- 11:49Performance comparison
- 12:51Failure recovery
- 13:12Conclusion
related talks
16mFORD: Fast One-sided RDMA-based Distributed Transactions for Disaggregated Persistent...
19mFast Distributed Transactions for RDMA-based Disaggregated Memory
14mVerifying vMVCC, a high-performance transaction library using multi-version concurrency..
01h 11mMVCC unmasked
25mDisaggregating Persistent Memory and Controlling Them Remotely
18mRDMA is Turing complete, we just did not know it yet!
16mOneSidedMW: Managing Disaggregated Memory Efficiently, Flexibly, and Securely with RNIC
12mCharacterizing and Optimizing Remote Persistent Memory with RDMA and NVM