-
Notifications
You must be signed in to change notification settings - Fork 46
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
Analyze performance regressions with Z3 after update to version 4.12.1 #292
Comments
I've written a program in native Z3 API and could not reproduce the slowdown. (see below)
|
Using the internal API of Z3, the String based task suddenly takes a very long time.
|
@baierd could you file an issue for Z3 with your information? Maybe @NikolajBjorner can help with the regression. |
Done: |
I've just tested the change in random seed for the parsed model (array) problem and it does not seem to change the issue present there. I've tried no random seed, as well as seeds 1, 2, 22, 43, 745638. I'll translate the model problem to internal API and update the Z3 issue. |
I've tested the current main branch after the update of our Z3 String issue, and the regression is gone! |
I found the time to finish the model/parsing issue program and opened a issue. |
Fixed in the newest main branch. Therefore both regressions should be gone by the next release of Z3. |
The new version of Z3 works fine on those tests.
With the latest version 4.12.1 of Z3, there are two performance regressions in our JUnit tests.
As temporary solution, the tests were disabled with the commit c1ad8c0.
For long-term solution, we should at least analyze the problem one step deeper, summarize the result, and create an example query or minimal Java program which can be reported back to the Z3 developers.
@baierd Feel free to add more info about the bugs within this issue.
The text was updated successfully, but these errors were encountered: