add --numsolvers to control the size of the solver pool - #232
Open
mijovic wants to merge 1 commit into
Open
Conversation
equiv sizes the solver pool with getNumProcessors and offers no way to override it. Each instance is a persistent solver process whose memory grows with the queries it has handled, so the practical limit is RAM, not cores: on a 32-core/61GiB machine, 32 bitwuzla instances reached ~1.6GiB each on an equivalence-heavy spec and the run had to be restarted with fewer. Defaults to the core count, so existing behaviour is unchanged. Only meaningful together with a -threaded build (otherwise getNumProcessors reports 1 and a single instance is spawned regardless).
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
1 participant
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.
Mergable after #230
equiv sizes the solver pool with getNumProcessors and offers no way to override it. Each instance is a persistent solver process whose memory grows with the queries it has handled, so the practical limit is RAM, not cores: on a 32-core/61GiB machine, 32 bitwuzla instances reached ~1.6GiB each on an equivalence-heavy spec and the run had to be restarted with fewer.
Defaults to the core count, so existing behaviour is unchanged. Only meaningful together with a -threaded build (otherwise getNumProcessors reports 1 and a single instance is spawned regardless).