-
Notifications
You must be signed in to change notification settings - Fork 37
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
Hanging mpire worker_pool.map_unordered #32
Comments
Would it be possible to provide a minimal working example where this happens? That would save me a lot of time. And please share the MPIRE version you're using, thnx. |
Without the worker_lifespan it works fine. |
Thnx for the example code. I can confirm that it indeed is hanging. I will have a look at this this week. |
Already found the culprit. Will try to find an elegant solution now. Fix will be available in next release of mpire |
…ults that exceed the pipe capacity (fixes #32)
Super, thanks
Op ma 21 feb. 2022 16:51 schreef Sybren Jansen ***@***.***>:
… Already found the culprit. Will try to find an elegant solution now
—
Reply to this email directly, view it on GitHub
<#32 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACH77I2SV4KRHYSFXT5EHV3U4JNO5ANCNFSM5N5ALP5A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Fixed in v2.3.4 |
When creating many processes which return large result, mpire will hang in collecting the results.
Analyzed is caused by crossing the system limit size for the os pipes, for linux defaults to 4K.
The text was updated successfully, but these errors were encountered: