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 asvetlov
Recipients Epic_Wink, Vojtěch Boček, asvetlov, methane, yselivanov
Date 2019-05-28.07:00:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1559026845.03.0.891892348724.issue35279@roundup.psfhosted.org>
In-reply-to
Content
I'm ok with changing the default threads number limit.
Not sure about numbers.
If you want to limit to 16-20 that may be ok but `cpu_count + 4` doesn't work in this case. On cloud servers, I see 128 or even more cores very often. 160+4 is not that you want to propose, sure.

I insist on changing the default calculation schema in concurrent.futures, not in asyncio. There is no case for asyncio to be exceptional.
History
Date User Action Args
2019-05-28 07:00:45asvetlovsetrecipients: + asvetlov, methane, yselivanov, Vojtěch Boček, Epic_Wink
2019-05-28 07:00:45asvetlovsetmessageid: <1559026845.03.0.891892348724.issue35279@roundup.psfhosted.org>
2019-05-28 07:00:45asvetlovlinkissue35279 messages
2019-05-28 07:00:44asvetlovcreate