https://bugs.openldap.org/show_bug.cgi?id=10395
--- Comment #9 from kero <[email protected]> --- Hello Howard and Happy New Year, We recently made use of this new deriving branch of LMDB in Meilisearch to reduce the indexing time of a large customer from 2 hours and 50 minutes to under 7 minutes. You can review the code here [1] if you are interested. It's really search-engine/inverted-index oriented, but still, the use of the `Env::nested_read_txn` method (creating a nested READ_ONLY transaction with a write transaction as a parent) makes it possible to read the current database in parallel. Did you have any chance to review my LMDB patch? It's working fine in production at Meilisearch since the last working version of my patch on LMDB, and it hasn't broken either our usage or the LMDB API. Have a nice begining of 2026, Looking forward for an answer, kero [1]: https://github.com/meilisearch/meilisearch/pull/6100/changes -- You are receiving this mail because: You are on the CC list for the issue.
