run booster with --no-fallback-simplify --no-post-exec-simplify #179
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
|
Proof runs from this PR are passing: https://github.com/runtimeverification/kasmer-multiversx/actions/runs/10159207265 |
bbyalcinkaya
approved these changes
Jul 31, 2024
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.
These two options can now be used because the booster simplification is mostly on par with the kore-rpc (fallback) one.
Running without the additional simplifications gives us quite a good speedup and the proofs are passing.
I have put the numbers into a comment here , the last line of the table is a run using these options (and latest
booster).(I did not test
all_tokens_claimed)If we add the options here it will be harder to override them, of course. My tests were using the
KORE_RPC_OPTSenvironment variable.