Add time-bounded executor & limit light client request processing time - #12725
Open
dmitry-markin wants to merge 4 commits into
Open
Add time-bounded executor & limit light client request processing time#12725dmitry-markin wants to merge 4 commits into
dmitry-markin wants to merge 4 commits into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add executor that aborts execution when timeout elapses, based on WasmTime epoch interruptions. A separate executor for time-bound requests is needed, because epoch interruption compiles into the WASM blob and slows execution down by 10%.
Limit light client execution proof requests by 3-second timeout by defaul. The timeout is deliberately chosen high before we obtain real-world execution time data for legitimate requests. The default timeout can be overridden with
--light-request-execution-timeout-ms.Review Notes
It is recommended to review the PR as a series of individual commits. They build on each other bottom-up.
See #12500 for original work and discussion.