LMDB – Lightning Memory-Mapped Database Manager

Re:LMDB – Lightning Memory-Mapped Database Manager by corysama on Sunday November 11, 2018 @12:28PM (#18427440)

I’ve used LMDB as a simpler alternative to SQLite as “an alternative to fopen”. The goal was simply robust file writes in the face of unpredictable server reboots for a tiny Python program writing data to be processed later by a tiny C++ program.

That’s harder than it sounds to roll by hand with fopen. SQLite with write ahead logging is pretty much as good as it gets for reliablity, but SQL at all was overkill for the task. LMDB is a close second and it’s memory mapped key-value interface is much simpler. . Would write again.

https://lwn.net/Articles/457667/

[ Parent | on HN ]

Re:LMDB – Lightning Memory-Mapped Database Manager by isaachier on Sunday November 11, 2018 @03:10PM (#18428295)

LMDB is a storage engine whereas SQLite is a small database. There is even a version of SQLite that used LMDB as the underlying storage engine: https://github.com/LMDB/sqlightning.

[ Parent | on HN ]

Re:LMDB – Lightning Memory-Mapped Database Manager by majidazimi on Sunday November 11, 2018 @03:10PM (#18428292)

LMDB's read performance crushes modern LSM databases. It's not an alternative to SQLite. It is well suited for read-heavy class of workloads.

[ Parent | on HN ]