Change multiprocessing methodology from Process to Pool.starmap. #9
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.
Hello
The existing code for handling processes in:
Looks something like:
This means that any time
len(procs) > max_procs
, you wait on all currently running processes to finish. This is inefficient because you will always be waiting on the slowest process to finish before starting any others.Instead, you can use
Pool.starmap
from multiprocessing.It works like this:
It means that as soon as one process finishes, another will start. In my tests, the time for the first 50 training sets to run went from 60 seconds to 12 seconds.
I have proposed changes to pu_learning.py because that was the only module I knew how to test. The same logic could easily be applied to the other three.