renegade_contracts: profiling: add breakpoints #86
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
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.
This PR adds the notion of "breakpoints" for key execution components we want to profile, providing an option to return early from our contract functions to get execution resource usage up to that point from the Katana devnet node.
The reason this is done in-process with an
enumis so that, when running the test/profiling suite, we can declare/deploy the contracts once and load state on subsequent profiling runs, instead of literally hardcoding an early return in the contracts and having to redeclare/redeploy every time we move it.Incorporating this change into the e2e tests / a small profiling suite is left for the next PR, so that any suggestions can be made here first.