Always schedule at least one job onto a core #1990
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
Even if the host configuration is returning `0` for the `lookahead`, we should schedule at least one job on a core if the core exists.
alindima
approved these changes
Oct 23, 2023
sandreim
approved these changes
Oct 23, 2023
|
Ideally the host configuration should be made sure to never have this set to 0. But that's better than nothing. |
bkchr
pushed a commit
that referenced
this pull request
Apr 10, 2024
* added receive_single_message_proof_with_dispatch benchmark * clippy
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.
Even if the host configuration is returning
0for thelookahead, we should schedule at least one job on a core if the core exists.