Patching LMDB: how we made Meilisearch’s vector store 3× faster
Mar 18, 2026Clément Renault

Summary
This post details a significant optimization to Meilisearch's vector store by patching LMDB to enable concurrent read transactions on uncommitted write transactions. This was achieved by implementing nested read-only transactions within a parent write transaction, allowing multiple threads to read uncommitted changes lazily on demand. This eliminates the need for a large, slow-to-initialize HashMap to store pointers, reduces cache pollution from full scans, and enables indexation to scale linearly with the number of CPUs, improving time complexity.
More from the Sharding and Replication trail
- How to diagnose search performance problems in B2B SaaS
- CarJager: Millions of Vehicle Searches on Meilisearch
- Meilisearch Launch Week April 2026 recap: everything that shipped
- Scale without limits: introducing sharding & replication in Meilisearch Cloud
- How Touchless powers instant, scalable vehicle search for large dealer groups