Fix handling of maxtasksperchild in ParallelExt for better compatibil… #1939
+5
−4
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.
Fix: Improve
ParallelExt
Compatibility withjoblib
BackendDescription
This PR fixes the handling of
maxtasksperchild
inParallelExt
, ensuring better compatibility when using thejoblib
backend. The update ensures that task management behaves consistently under different multiprocessing settings.Motivation and Context
Previously,
maxtasksperchild
was either not respected or caused unexpected behavior under thejoblib
backend. This change ensures that task recycling and memory/resource constraints are correctly handled when running long or parallel workflows.How Has This Been Tested?
pytest qlib/tests/test_all_pipeline.py
Please confirm the above after testing.
Screenshots of Test Results (if appropriate)
(You can attach console output or screenshots here if needed)
Types of Changes