fix validate_rpcs. Run RPC compute heavy jobs in a thread pool #19922
Conversation
This file contains hidden or 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
aqk
added
the
Changed
|
Looks good. Nice change with the |
arvidn
commented
Aug 8, 2025
arvidn
commented
Aug 8, 2025
|
https://github.com/oleglpts/PriorityThreadPoolExecutor really need something like this ideally, but the additional pool keeps things proportional for now |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Purpose:
validate_rpcs.py, when validating all 3 RPC calls, would not limit the number of concurrent outstanding requests properly.Also, use a thread pool to actually run the blocks, rather than the main thread.