Re: LMDB vs FastDB

FastDB also appears to use locking, while LMDB is MVCC and readers

Yeah, MVCC is the right thing ..

require no locks, so even with all of the other disadvantages out of the way, LMDB will scale better across multiple CPUs.

So _one_ LMDB can be concurrently used from multiple threads and multiple processes, with multiple readers and writers?

Writers wont block readers, but writers require exclusive lock?

When used from different process, the single-layer design making use of the filesystem buffer cache will mean there is no "buffer cache" per process, and memory-consumption won't skyrocket?

Tobias