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 pitrou
Recipients benjamin.peterson, daniel.urban, jcon, pitrou, stutzbach
Date 2011-05-08.15:49:22
SpamBayes Score 2.585745e-06
Marked as misclassified No
Message-id <1304869759.3541.1.camel@localhost.localdomain>
In-reply-to <1304804624.01.0.325988568291.issue9971@psf.upfronthosting.co.za>
Content
> The trade-off of accommodating a small buffer size (by buffering
> behind the scenes anyways) would likely slow the more common cases
> which use a decent buffer size. I am wondering if an effort to
> accommodate both uses would be appropriate. Possibly by not
> double-buffering if readinto(b): len(b) > buffer_size/2 (arbitrary but
> seems feasible), and copying directly as the patch does now.
> Otherwise, fill the buffer up for subsequent reads and copy len(b) to
> user buffer. There is probably a good equilibrium for when it makes
> more/less sense to bypass the internal buffer.

Yes, it sounds reasonable. I think the best thing to do is to experiment
and run some measurements.
History
Date User Action Args
2011-05-08 15:49:25pitrousetrecipients: + pitrou, benjamin.peterson, stutzbach, daniel.urban, jcon
2011-05-08 15:49:23pitroulinkissue9971 messages
2011-05-08 15:49:22pitroucreate