perf: Speed up storage_reservation_test#9514
Merged
alin-at-dfinity merged 2 commits intomasterfrom Mar 23, 2026
Merged
Conversation
The test ran with the default subnet memory capacity of 2 TB, meaning that the stable memory growth test required executing many hundreds of ingress messages (4 GB at a time). Plus, because we used the default 4 scheduler cores, each stepdown in page size required 4 up to allocations / stable_grow calls. Reduce the memory capacity to 4 GB (threshold at 2 GB). And the number of scheduler cores to 2. Test runtime drops from 50-100 seconds to under 1 second.
alin-at-dfinity
changed the title
storage_reservation_teststorage_reservation_test
adambratschikaye
approved these changes
Mar 23, 2026
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
2 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.
The test ran with the default subnet memory capacity of 2 TB, meaning that the stable memory growth test required executing many hundreds of ingress messages (4 GB at a time). Plus, because we used the default 4 scheduler cores, each step down in page size required 4 up to allocations /
stable_growcalls.Reduce the memory capacity to 4 GB (threshold at 2 GB). And the number of scheduler cores to 2.
Test runtime drops from 50-100 seconds to under 1 second.