[scheduler] Another task-stealing optimization #9984
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.
The main win here is the third commit.
It is a followup to #9594, and was tested in prod on multiple kinds of machines and multiple services.
We observed some small but significant wins in scheduler utilisation, including at peak load which was the weak point of the previous batch of optimisations.
cc @tomas-abrahamsson since you saw large wins from the previous batch of scheduler enhancements.