Snapshot txMeta without cloning history #8363
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.
Refs #6547 (comment)
This PR updates how we snapshot
txMeta
objects, cloning them without the history instead of cloning the history and then throwing it away. This should improve the performance ofTransactionStateManager#updateTx
when the transaction has a particularly large history.There is a test to confirm that the history property is excluded—this is an implementation detail.