[cfg] Using multiprocess lib instead of multiprocessing #4076
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
The standard `multiprocessing` lib has some issues mainly in Mac environment. Also, in Linux environment, too small system resources cause CodeChecker analyzer processes hang: If the maximum number of processes (`ulimit -u`) is too small, then allocating a process pool with the standard `multiprocessing` lib raises a RuntimeError that can't be handled. With `multiprocess` lib another kind of exception is thrown, but the process itself doesn't hang.
bruntib
added
CLI 💻
dkrupp
approved these changes
Nov 16, 2023
|
fixes #4079 |
This was referenced Nov 16, 2023
Closed
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.
The standard
multiprocessinglib has some issues mainly in Mac environment. Also, in Linux environment, too small system resources cause CodeChecker analyzer processes hang:If the maximum number of processes (
ulimit -u) is too small, then allocating a process pool with the standardmultiprocessinglib raises a RuntimeError that can't be handled. Withmultiprocesslib another kind of exception is thrown, but the process itself doesn't hang.