Feat/lazy load deployment #2553
Open
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.
Motivation (from original PR)
We've seen that RSS size is correlated with deployments loaded (and staying) in memory. This PR keeps MAX_STACKS programs in memory (chosen arbitrarily at 1000).
Test Plan
Tested by running a local and deployed devnet, deploying programs and executing them. Then restarting the network and trying to execute these programs. The Stacks were lazily loaded from storage, execution worked. Also tested executing programs that are not deployed.
Related PRs
Replaces #2519