This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author aeros
Recipients aeros, asvetlov, vstinner, yselivanov
Date 2019-10-26.17:12:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1572109954.17.0.280718265206.issue38591@roundup.psfhosted.org>
In-reply-to
Content
> But it spawns a new Python thread per process which can be a blocker issue if a server memory is limited.

I understand that there's *some* overhead associated with spawning a new thread, but from my impression it's not substantial enough to make a significant impact in most cases. Each individual instance of threading.Thread is only 64 bytes. Have you seen any recent cases where the server memory is limited enough for the memory cost associated with having to spawn an additional thread per subprocess becomes the limiting factor?
History
Date User Action Args
2019-10-26 17:12:34aerossetrecipients: + aeros, vstinner, asvetlov, yselivanov
2019-10-26 17:12:34aerossetmessageid: <1572109954.17.0.280718265206.issue38591@roundup.psfhosted.org>
2019-10-26 17:12:34aeroslinkissue38591 messages
2019-10-26 17:12:34aeroscreate