chore: update max compute unit config and bump version #119
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 change updates the CU limit to make sure that price updates with more than 32 publishers have enough CU. Number 38k is obtained based on adjusting
test_full_publisher_settest on the oracle to run in multiple rounds with random price updates to make sure worst case sorting is reached. Unfortunately there was no way to test it with CPI to accumulator (message buffer) and that number is taken based on current tx usage and the extra buffer is there because there are some extra logic in the oracle for oracle as well and the CU limit is not applied in transaction scheduling.