Cow snapshots instead of always cloning #161
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To satisfy LMDB's semantics, querying or modifying individual transactions has certain behavior guarantees. Each transaction is a snapshot of the database; in other words, multiple read/write transactions are views into the database at the beginning of the transaction, altering or querying independent of each other.
To do this in safe mode, we create database snapshots when instantiating transactions (cloning on read). This is needlessly precautious, we can opt for cloning on write instead. This PR improves performance in case of large databases and the usual use of transactions.