https://bugs.openldap.org/show_bug.cgi?id=10395
kero <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #1089|0 |1 is obsolete| | --- Comment #6 from kero <[email protected]> --- Created attachment 1096 --> https://bugs.openldap.org/attachment.cgi?id=1096&action=edit Last patch to allow multiple nested read transactions from a write transaction Hey Howard, I have finalized the last version of this patch. Would you mind taking a look at it, please? We are using this patched version of LMDB in production with large datasets, and it performs exceptionally well. We are capable of multi-threading the reads we perform on uncommitted changes. If you are not eager to merge this patch, could you please explain why? I am not quite sure I understand: We are not introducing concurrent modifications of the write transaction's content, nor allowing external read transactions to read uncommitted content. Only the program owning the write transaction can perform reads in parallel, which it was already allowed to do, but not in parallel before. Side note: Would you mind updating the GitHub mirror of LMDB, please? There is a missing commit[1]. [1]: https://github.com/LMDB/lmdb/commit/1db2a61ade6ae087dc175b1f44303548a4aa7926 Have a nice end of the week, Thank you, kero -- You are receiving this mail because: You are on the CC list for the issue.
