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 vinay.sajip
Recipients Brian.Cain, Ian.Davis, Matt.Goodman, jnoller, neologix, osvenskan, terry.reedy, vinay.sajip
Date 2011-08-27.15:13:02
SpamBayes Score 3.0104939e-05
Marked as misclassified No
Message-id <1314457983.87.0.672335182627.issue8426@psf.upfronthosting.co.za>
In-reply-to
Content
I think it's just a documentation issue. The problem with documenting limits is that they are system-specific and, even if the current limits that Charles-François has mentioned are documented, these could become outdated. Perhaps a suggestion could be added to the documentation:

"Avoid sending very large amounts of data via queues, as you could come up against system-dependent limits according to the operating system and whether pipes or sockets are used. You could consider an alternative strategy, such as writing large data blocks to temporary files and sending just the temporary file names via queues, relying on the consumer to delete the temporary files after processing."
History
Date User Action Args
2011-08-27 15:13:04vinay.sajipsetrecipients: + vinay.sajip, terry.reedy, osvenskan, jnoller, neologix, Ian.Davis, Brian.Cain, Matt.Goodman
2011-08-27 15:13:03vinay.sajipsetmessageid: <1314457983.87.0.672335182627.issue8426@psf.upfronthosting.co.za>
2011-08-27 15:13:03vinay.sajiplinkissue8426 messages
2011-08-27 15:13:02vinay.sajipcreate