Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add option: use_max_threads #2528

Merged
merged 1 commit into from May 9, 2022
Merged

Conversation

seros1521
Copy link
Contributor

Allows to backup using the maximum number of threads, without using
autotuning (but not more than the maximum)

Pre-Request Checklist

  • Passes rubocop code analysis (try rubocop --auto-correct)
  • Tests added or adapted (try rake test)
  • Changes are reflected in the documentation
  • User-visible changes appended to CHANGELOG.md

Description

Fixes #2527

@mortzu
Copy link
Collaborator

mortzu commented May 2, 2022

Can you please fix the conflict

Allows to backup using the maximum number of threads, without using
autotuning (but not more than the maximum)
@seros1521
Copy link
Contributor Author

Fixed.

@mortzu mortzu merged commit 7b5c129 into ytti:master May 9, 2022
@seros1521 seros1521 deleted the use_max_threads branch May 11, 2022 11:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Enhancement request: forced-multithread operation to support "snapshot"-like collection
2 participants