apply partitioned dml via worker pool #58
Merged
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
RoryQ
force-pushed
the
partitioned-dml-concurrency
branch
from
bcf53ac to
7623926
Compare
RoryQ
force-pushed
the
partitioned-dml-concurrency
branch
from
7623926 to
5416891
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
This change allows configuration of the concurrency level of the partitioned DML updates.
WHY
Partitioned DML updates are not very useful unless they are executed concurrently. This results in faster updates when there are a lot of statements since spanner allows these self-transactional updates to happen concurrently.