-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Haskell-Performance] kevm proof slow with extra side conditions #3286
Comments
@F-WRunTime it seems that it cannot detect that I'm a member of the org? https://github.com/runtimeverification/haskell-backend/actions/runs/3148634684/jobs/5119382938 |
dummy comment to trigger workflow |
Test me. |
1 similar comment
Test me. |
Ran the two tarballs in a separate ticket #3303 . Nothing immediately suspicious in the profiles, but the top consumers differ to significant extent:
|
Blocked on #3113, because the highest cost center is hashing. After that is fixed, we should reinvestigate. |
Please Prepare Test Data
I have a specification on KEVM: https://github.com/runtimeverification/evm-semantics/blob/master/tests/specs/benchmarks/storagevar03-spec.k
This can be run with:
make tests/specs/benchmarks/storagevar03-spec.k.prove
after building KEVM.It has some side-conditions for validity on the input state: https://github.com/runtimeverification/evm-semantics/blob/master/tests/specs/benchmarks/storagevar03-spec.k#L116. But these side-conditions are actually not needed (the lines
CONTRACT_ID >Int 0 andBool notBool #isPrecompiledAccount(CONTRACT_ID, BYZANTIUM)
), so I removed them.Removing these 4 conditions (on
CONTRACT_ID
andCALLEE_ID
) ends up improving the performance by ~2.5X.So it seems that having these extra side-conditions is causing a big performance slowdown.
I've attached 2 bug reports:
These conditions should not change their simplification status through the whole proof beyond startup, so I guess I'm wondering why it takes so much longer to run with these extra conditions. We should try evaluating them once, and then basically know that they can't be simplified any further throughout the rest of execution (so should not try).
The text was updated successfully, but these errors were encountered: