Avoid using thread-local WriteSet when possible #3829
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.
Motivation
For computing WriteSet we use a
Recycler
to avoid instantiating a new object each time. While that avoid allocations, it's based on thread-locals and has non-zero cost.In most cases the usage of WriteSet that we are doing is very basic:
WriteSet
from the recyclerInstead, we can just expose a method in the
DistributionSchedule
interface and avoid any recycler or object allocations.