Message220966
| Author |
vstinner |
| Recipients |
Sebastian.Kreft.Deezer, giampaolo.rodola, gvanrossum, pitrou, python-dev, vstinner, yselivanov |
| Date |
2014年06月19日.11:10:16 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1403176217.29.0.750865725352.issue21595@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
I commited asyncio_read_from_self.patch into Tulip, Python 3.4 and 3.5. If someone is interested to work on more advanced enhancement, please open a new issue.
Oh by, a workaround is to limit the number of concurrent processes.
Without the patch, "./python test_subprocess_error.py 5 1000" (max: 5 concurrenet processes) emits a lot of "BlockingIOError: [Errno 11] Resource temporarily unavailable" message.
With the patch, I start getting messages with 140 concurrent processes, which is much better :-) IMO more than 100 concurrent processes is crazy, don't do that at home :-) I mean processes with a very short lifetime. The limit is the number of SIGCHLD per second, so the number of processes which end at the same second. |
|