-
-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Process mode does not respect the number of threads #8
Comments
Hey! I would love it if you can suggest a fix via a pull request :) Thanks, |
? |
Sorry Ran, this fell through the cracks. I'm travelling now but will propose a fix when I return in a week or 2. |
? |
Hi Ran, I hope this is better late than never. Unfortunately, I do not have permission from my employer to contribute to Open-Source projects. However, if you find the following helpful you are welcome to do with it as you see fit. Best Wishes, Bishop Brock
|
Hi Ran,
Thank you for fixing the issues I mentioned a few days ago. I noticed another issue recently: When using processes, you can not limit the number of running processes, because _run_via_pool() is using the threading semaphore, and the task has already started in a new process when it acquires the semaphore. (This is important to me because I'll run out of memory if all of the processes run simultaneously).
If you'd like I could suggest a fix via a pull request, but I think all that's needed is to import both types of Semaphore and make sure the correct one is used in createPool().
Thanks,
Bishop Brock
The text was updated successfully, but these errors were encountered: