"Non Volatile Memory" really means Intel's "3D X-point" memory-- estimated availability of this product for system memory is 2018-ish. http://www.tomshardware.com/news/intel-optane-cascade-lake-d...
Optane is on sale now.
How to Build a Non-Volatile Memory DBMS
11–20 of 37 posts
Re: How to Build a Non-Volatile Memory DBMS
#12"Non Volatile Memory" really means Intel's "3D X-point" memory-- estimated availability of this product for system memory is 2018-ish. http://www.tomshardware.com/news/intel-optane-cascade-lake-d...
Optane is on sale now.
Optane's performance is hardly on par with SSDs, let alone DRAM.
XPoint is expected to have performance much higher than Optane.
Re: How to Build a Non-Volatile Memory DBMS
#13Re: How to Build a Non-Volatile Memory DBMS
#14"Non Volatile Memory" really means Intel's "3D X-point" memory-- estimated availability of this product for system memory is 2018-ish. http://www.tomshardware.com/news/intel-optane-cascade-lake-d...
HP has NVDIMMs that you can order for the DL series of servers. I'm waiting on a POC machine with 16GB of NVDIMM right now.
Re: How to Build a Non-Volatile Memory DBMS
#15Earlier quoted context omitted.
Optane's performance is hardly on par with SSDs, let alone DRAM. XPoint is expected to have performance much higher than Optane.
Optane is the "marketing name" the technology behind Optane is 3D-XPoint.
The Optane available currently isn't in DIMM-format which is expected to give a further boost though.
Re: How to Build a Non-Volatile Memory DBMS
#16>Assistant Professor of Databaseology Oh, I didn't know that's a thing.
Sounds like Indiana Jones. Data mining ancient databases.
Re: How to Build a Non-Volatile Memory DBMS
#17The presentation and the paper pretty much describe how LMDB works already. https://symas.com/lightning-memory-mapped-database/ Except, it allows only a single writer and it's not directly byte-addressable, unless you make a request to preallocate a chunk of fixed-size mmap'ed memory.
Yes but in byte-addressable mode you can trust the map is fixed, which doesn't seem to be the case here.
Re: How to Build a Non-Volatile Memory DBMS
#18Earlier quoted context omitted.
Optane is the "marketing name" the technology behind Optane is 3D-XPoint.
The Optane available currently isn't in DIMM-format which is expected to give a further boost though.
This is true. Bypassing the page cache and VFS will be a net win. But all my storage needs can't be done in MMAPs
Re: How to Build a Non-Volatile Memory DBMS
#19"Non Volatile Memory" really means Intel's "3D X-point" memory-- estimated availability of this product for system memory is 2018-ish. http://www.tomshardware.com/news/intel-optane-cascade-lake-d...
There is also MRAM [0] which ships from a company called Everspin [1][2] and is produced by Globalfoundries. Unlike Intels/Microns solution it seems to be as fast as normal RAM, but at much smaller densities.
[0] https://en.wikipedia.org/wiki/MRAM
[1] https://www.everspin.com/ddr3-dram-compatible-mram-spin-torq...
Re: How to Build a Non-Volatile Memory DBMS
#20The presentation and the paper pretty much describe how LMDB works already. https://symas.com/lightning-memory-mapped-database/ Except, it allows only a single writer and it's not directly byte-addressable, unless you make a request to preallocate a chunk of fixed-size mmap'ed memory.
Yes but in byte-addressable mode you can trust the map is fixed, which doesn't seem to be the case here.
Not exactly. I'm not a user of this, but
http://www.lmdb.tech/doc/group__mdb__env.html#ga492952277c48...
Ctrl+f through the doc for "MDB_FIXEDMAP" for more details.
So there is _some_ support, where you can expect to have the whole file at a fixed address. What is not handled is that your data may be moved within the file, and there's nothing you can do about it, short of keeping a long-lived read only transaction: