Conversation
Frame solvers accumulate deactivated variables from releaseVar calls. After 2000 queries, the internal variable tables become bloated, slowing unit propagation. Recycling rebuilds the solver from the base CNF plus current frame clauses, restoring performance. The limit of 2000 balances the cost of rebuilding (replaying the base CNF + frame clauses) against the degradation from accumulated dead variables. On large benchmarks this prevents a gradual 2-5x slowdown in later frames.
Collaborator
|
Why is 2000 the right number? And is that really the most appropriate solution? Is there no proper |
This branch has not been deployed
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.
Summary
SOLVER_RECYCLE_LIMITconstant andframe_solver_queriesvectorIndividual benefit
Prevents 2-5× gradual slowdown in later frames. Frame solvers accumulate deactivated variables from
releaseVarcalls; after many queries the internal variable tables bloat, degrading unit propagation performance. Recycling restores a clean solver state.Synergies
satchecktsolver in IC3 #6) which increase per-frame query countsTest plan
regression/ebmc/new-ic3passes-Werror(GCC)