-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Avoid hangs on many-core Windows machines #7035
Conversation
Creating a multiprocessing Pool with too many processes can hit ValueError exceptions or hangs or both. The number that counts as "too many" depends on the Python version so this change uses 56 as a guaranteed safe limit. Details in issue 6965 Note that this only avoids the issue if an explicit jobs count is not passed in.
for more information, see https://pre-commit.ci
doc/whatsnew/2/2.15/index.rst
Outdated
|
||
* Fixed an issue where many-core Windows machines (>~60 logical processors) would hang when | ||
using the default jobs count. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We're going to backport that in 2.14.4 :)
Thank you for the research you've done @randomascii, much appreciated ! |
You're welcome. It was interesting, and the discussion on the bug was helpful for me. |
Pull Request Test Coverage Report for Build 2559891737
💛 - Coveralls |
This comment has been minimized.
This comment has been minimized.
for more information, see https://pre-commit.ci
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only need to move the changelog entry to 2.14.4
.
Thanks very much for all the work here @randomascii! Much appreciated!
I updated 2.15/index.rst and put the same content in 2.14/index.rst - I hope that is as desired. I also made the requested comment change (I didn't see the button to do it from the pull request until I'd already done it on my machine). |
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I move the changelog to the 2.14.4
section as that will be the release this will be available in. Should have been clearer about that!
Thanks a lot @randomascii 😄
This comment has been minimized.
This comment has been minimized.
🤖 According to the primer, this change has no effect on the checked open source code. 🤖🎉 This comment was generated for commit 7c709da |
Creating a multiprocessing Pool with too many processes can hit ValueError exceptions or hangs or both. The number that counts as "too many" depends on the Python version so this change uses 56 as a guaranteed safe limit. Details in pylint-dev#6965 Note that this only avoids the issue if an explicit jobs count is not passed in. Co-authored-by: Daniël van Noord <13665637+DanielNoord@users.noreply.github.com>
Creating a multiprocessing Pool with too many processes can hit ValueError exceptions or hangs or both. The number that counts as "too many" depends on the Python version so this change uses 56 as a guaranteed safe limit. Details in #6965 Note that this only avoids the issue if an explicit jobs count is not passed in. Co-authored-by: Daniël van Noord <13665637+DanielNoord@users.noreply.github.com>
Creating a multiprocessing Pool with too many processes can hit
ValueError exceptions or hangs or both. The number that counts as "too
many" depends on the Python version so this change uses 56 as a
guaranteed safe limit.
Note that this only avoids the issue if an explicit jobs count is not
passed in.
| ✓ | 🐛 Bug fix |
Closes #6965