- MICA: A Holistic Approach to Fast In-Memory Key-Value Storage
- Boosting Timestamp-based Transactional Memory by Exploiting Hardware Cycle Counters
- Message Passing or Shared Memory: Evaluating the Delegation Abstraction for Multicores
- NVMCached: An NVM-based Key-Value Cache
- The Future of Synchronization on Multicores: The Mulitcore Transformation
- Conferences Journals and Workshops
- Distributed Systems
- File Systems
- Key-Value Stores
- Media File Systems
- Name Spaces
- Network File Systems
- Non-Volatile Memory
- Operating Systems
- Research Ideas
- Semantic File Systems
Subscribe to Blog via Email
I’ve been gone for a bit; real life keeping me busy. Part of that has been exploring the current edge of my technology space. So I’m going to take a break from the historical paper review (but it will come back) and instead start talking about new storage technologies and the interesting things that we can do with them.
Specifically, I have been looking at the brave new world of “non-volatile dual inline memory modules”. What this means is that we now have persistent memory that is directly accessed via processor primitives. That means a load or a store instruction can be used to access this kind of memory. We have actually been talking about persistent memory since the dawn of time. Many of the early operating systems papers think of disk storage and memory as being different forms of memory.
The big change here was when computers moved away from magnetic core memory into solid state memory. Intel’s first product was dynamic RAM (though it was invented by IBM). DRAM was cheaper and faster than core – and much faster than magnetic storage. Thus the abstraction of memory and disk being part of the same continuum we began to think of them as being distinct. DRAM was transient; disks and tapes were persistent (note that magnetic core was persistent until someone read it, at which point it lost its state and had to be rewritten – even across power cycles).
Disk storage was often used to contain data from memory, such as for paging or segmentation. Over the years the operating systems community learned many ways to make disks seem fast: caching, read-ahead, asynchronous I/O, reordering operations, etc.
Computers – and memory – were able to experience vast increases in speed. Disk drives did improve, but only modestly in comparison.
Memory technologies have continued to evolve. Persistent memory options increased as well; flash memory is one of the most common today and is used inside solid state drives and NVMe disks, both of which are vastly faster than rotating media disks.
Another memory technology that has been discussed for more than 20 years has been persistent RAM. One way this has been done in “real products” has been to simply add a backup power source: some sort of battery. Then if the power is lost, the data contents of volatile memory (DRAM) can be written to persistent storage (e.g., Flash). This approach has been a stop-gap on the way to the actual persistent memory solution that has been promised for at least a decade: persistent memory that acts like DRAM. Intel is now starting to ship their new Optane memory products. Samsung has announced their new Z-NAND products. Other technologies remain “in development” as well.
Why does this matter? Storage is suddenly getting faster. We went from 10 millisecond access times to 0.2 millisecond access times (HDDs to SSDs). Now we are looking at going from 0.2 milliseconds to 200 nanoseconds – six orders of magnitude faster. This sort of change is profound. We’ve been talking about it for many years, trying to reason about it. It is now materializing. Over the next several years the other promise of NVM is going to materialize: it supports higher density than DRAM. It is slower than DRAM; where DRAM access times are on the order of 50-100 nanoseconds, NVM access times are on the order of 125-800 nanoseconds (writes being slower than reads).
File systems that have been optimized for working on hard disks or SSDs don’t necessarily make sense on NVM.
Thus, the area I’ve been looking at: expanding my own understanding of NVM. Since this is still related to my own exploration of file systems, I’ll use this as my soapbox for exploring the space.
Let’s see where this journey goes. And I promise, I’ll come back to the old file systems papers after this diversion.