[FIX] peakfit: limit multiprocessing to 2 processes during fitting to avoid crashes #748
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
…uasars#743) Can be overridden with new env var QUASAR_N_PROCESSES=all
markotoplak
changed the title
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.
Fixes #743
Can be overridden with new env var
QUASAR_N_PROCESSES=allDocumented in the widget documentation. We can move it later if we use it more places.
I was going to add tests* but it seems
unittestalways gives youcpu_count()==1(so that part works at least) and mocking environment variables inunittestis annoying.Edit: I did test the permutations on a large multicore machine