3 ms·
Is this the reason for your observation that LMDB is oriented towards read workloads? I can see how the extra code locking/concurrency code would expand the li
by rossjudson 13y ago
Is this the reason for your observation that LMDB is oriented towards read workloads?
I can see how the extra code locking/concurrency code would expand the library size out of the CPU cache, though.
- hyc_symas 13y agoYes, since readers don't require any locks at all and don't issue any blocking calls of any kind - syscalls, malloc, whatever - they run completely unimpeded. The moment you introduce fine-grained locks of any kind the overall performance (reads and writes) will decrease by at least an order of magnitude because readers will have to deal with lock contention.