Lightning Memory-Mapped Database Manager (LMDB) 1.0
1–10 of 73 posts
Re: Lightning Memory-Mapped Database Manager (LMDB) 1.0
#2New features in LMDB 1.0 include:
- support for incremental backup
- support for page-level checksums and encryption
- support for DB on raw block devices
- support for 2-phase commit
- support for page sizes up to 64KB
plus other minor additions to the API.
Re: Lightning Memory-Mapped Database Manager (LMDB) 1.0
#3HTTP ?? Com’on man
Re: Lightning Memory-Mapped Database Manager (LMDB) 1.0
#4HTTP ?? Com’on man
it is just a link to documentation
Re: Lightning Memory-Mapped Database Manager (LMDB) 1.0
#5Re: Lightning Memory-Mapped Database Manager (LMDB) 1.0
#6Do people have good experiences with LMDB, in terms of reliability? I've never used it in production, but I've read through the code and design documents for a database implementation class.
I remember some strange code (such as pushing return values 4k above the stack, with a comment like "this works as long as the caller doesn't use more than 4k of stack space before accessing the return value"), and the author also shared some unconventional opinions about undefined behavior (like "Compilers are deterministic, if I know what platform I'm compiling to then no behavior is undefined. And if compiler authors disagree, they are morons.")
But presumably it's thoroughly tested, so those aren't problems in practice? Would be really interested to hear from people who've actually used it. I've mainly stuck to SQLite instead.
Re: Lightning Memory-Mapped Database Manager (LMDB) 1.0
#7Earlier quoted context omitted.
it is just a link to documentation
TLS certs are freeeeee
Judging from this very release, where he implemented support for page-level checksums and encryption for LMBD, I assume the author knows a thing or two about encryption. He probably then deemed it unnecessary for this specific website.
Re: Lightning Memory-Mapped Database Manager (LMDB) 1.0
#8Do people have good experiences with LMDB, in terms of reliability? I've never used it in production, but I've read through the code and design documents for a database implementation class. I remember some strange code (such as pushing return values 4k above the stack, with a comment like "this works as long as the caller doesn't use more than 4k of stack space before accessing the return value"), and the author als…
It has been used successfully as the backend for OpenLDAP and Monero, at least.
Re: Lightning Memory-Mapped Database Manager (LMDB) 1.0
#9Maybe rephrase this part - "It is read-only by default as this provides total immunity to corruption. Using read-write mode offers much higher write performance, but adds the possibility for stray application writes thru pointers to silently corrupt the database."
I generally do think read-write mode would offer higher write performance than read only as well :)
Re: Lightning Memory-Mapped Database Manager (LMDB) 1.0
#10Do people have good experiences with LMDB, in terms of reliability? I've never used it in production, but I've read through the code and design documents for a database implementation class. I remember some strange code (such as pushing return values 4k above the stack, with a comment like "this works as long as the caller doesn't use more than 4k of stack space before accessing the return value"), and the author als…
Be cautious if you're using large databases on iOS. At least until fairly recently, iOS doesn't page dirty mmaped pages back to disk and after enough churn the app will OOM.