Use spawn_async in ByRoot handling workers #5557
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.
Issue Addressed
Work::BlocksBy.*Request
are the only two work events usingspawn_blocking_with_manual_send_idle
. Its syntax prevents the use of helpful patterns like:So far it's unclear to me why this specific work needs to use such an executor pattern. Serving blocks should be a purely i/o bound task with any long blocking CPU tasks. One expensive op dug there is forwards_iter_block_roots cloning the entire head state, but I'm unsure if it justifies the pattern.
I lack the historical context to declare this solution proper, but I'm opening this PR to trigger a conversation.
Proposed Changes
Use spawn_async in ByRoot handling workers