Set max_final_threads
to number of cores by default
#47915
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.
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Setting
max_final_threads
would be set to number of cores at server startup (by the same algorithm as we use formax_threads
). This improves concurrency offinal
execution on servers with high number of CPUs.So the new behaviour is:
max_final_threads != 0
=> value left untouched, otherwisemax_threads = cpus
. additionally ifmax_final_threads > max_threads
=>max_threads
streams will be used for reading.