[#2536] feat(spark): Controllable concurrency for overlapping compression #2541
Conversation
This file contains hidden or 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
3 tasks
|
cc @jerqi |
|
Merged. |
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 changes were proposed in this pull request?
Introduce extra the option to control the concurrency of overlapping compression.
Why are the changes needed?
for #2536 .
Decoupling compression concurrency from the transfer pool is essential for resource isolation and performance stability, especially under multi-tenant or CPU-constrained environments.
Does this PR introduce any user-facing change?
Yes.
rss.client.write.overlappingCompressionThreads=-1.About overlapping compression related config options, I will add it into doc in another PR
How was this patch tested?
Unit tests.