Message 176491 - Python tracker

➜

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	felipecruz
Recipients	felipecruz
Date	2012-11-27.20:37:33
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1354048654.58.0.545467206879.issue16565@psf.upfronthosting.co.za>
In-reply-to

Content
Current pending calls limit is too small and it can be easily reached in very intensive async file io applications. There is a little hack in pyaio[1] which sleeps if Py_AddPendingCall returns < 0 but It's not totally clear to me why the size of pendind calls array is only 32. [1] https://github.com/felipecruz/pyaio

Current pending calls limit is too small and it can be easily reached in very intensive async file io applications.

There is a little hack in pyaio[1] which sleeps if Py_AddPendingCall returns < 0 but It's not totally clear to me why the size of pendind calls array is only 32.


[1] https://github.com/felipecruz/pyaio

History
Date	User	Action	Args
2012-11-27 20:37:34	felipecruz	set	recipients: + felipecruz
2012-11-27 20:37:34	felipecruz	set	messageid: <1354048654.58.0.545467206879.issue16565@psf.upfronthosting.co.za>
2012-11-27 20:37:34	felipecruz	link	issue16565 messages
2012-11-27 20:37:33	felipecruz	create