Use Concurrent.available_processor_count
instead of Concurrent.usable_processor_count
#2358
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.
Description
Concurrent.usable_processor_count
changed toConcurrent.available_processor_count
while code review so, we should use ``Concurrent.available_processor_count`.Concurrent.available_processor_count
maybe returnnil
. In those cases, I think we should useprocessor_count
.aws-sdk-rails
adapted similar logic. https://github.com/aws/aws-sdk-rails/blob/38117a13edc13623e42be5c180bd7d25892faba5/lib/aws/rails/sqs_active_job/executor.rb#L12