Persistent Memory Transactions

• Published in: arXiv.org 2018-03
• Main Authors: Marathe, Virendra, Mishra, Achin, Trivedi, Amee, Huang, Yihe, Zaghloul, Faisal, Kashyap, Sanidhya, Seltzer, Margo, Harris, Tim, Byan, Steve, Bridge, Bill, Dice, Dave
• Format: Article
• Language: English
• Subjects: Computer memory; Plugs; Run time (computers); Synchronism
• ISSN: 2331-8422

This paper presents a comprehensive analysis of performance trade offs between implementation choices for transaction runtime systems on persistent memory. We compare three implementations of transaction runtimes: undo logging, redo logging, and copy-on-write. We also present a memory allocator that plugs into these runtimes. Our microbenchmark based evaluation focuses on understanding the interplay between various factors that contribute to performance differences between the three runtimes -- read/write access patterns of workloads, size of the persistence domain (portion of the memory hierarchy where the data is effectively persistent), cache locality, and transaction runtime bookkeeping overheads. No single runtime emerges as a clear winner. We confirm our analysis in more realistic settings of three "real world" applications we developed with our transactional API: (i) a key-value store we implemented from scratch, (ii) a SQLite port, and (iii) a persistified version of memcached, a popular key-value store. These findings are not only consistent with our microbenchmark analysis, but also provide additional interesting insights into other factors (e.g. effects of multithreading and synchronization) that affect application performance.