Updated text to clarify performance vs serializability tradeoff #348
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
benmeadowcroft
force-pushed
the
master
branch
from
30f2038
to
f23acb9
Compare
Signed-off-by: Ben Meadowcroft <[email protected]>
Signed-off-by: Ben Meadowcroft <[email protected]>
benmeadowcroft
force-pushed
the
master
branch
from
bb930f9
to
ee352e6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What is changed?
Updated the documentation to clarify on what characteristic (performance related) snapshot isolation was better than serializability and why it was the default.
The current doc reads that snapshot isolation has better serializability (than the serializability option). However this is not the case, the tradeoff is that it has better performance, with a limited impact on serializability.
Any related PRs or issues?
No
Which version does your change affect?
Latest