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 Arfrever, alexandre.vassalotti, asvetlov, neologix, pitrou, rhettinger, serhiy.storchaka
Date 2013-04-27.10:38:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1367059107.2540.4.camel@fsol>
In-reply-to <>
> 1. Pack picked items in blocks of some predefined (or specified at the
> start with the BLOCKSIZE opcode) size. Only some large data (long
> strings, large integers) can cross the boundary between blocks. In all
> other cases the block should be padded with the NOP opcode.

Padding makes it both less efficient and more annoying to handle, IMO.
My framing proof-of-concept ends up quite simple in terms of code
complexity. For example, the C version only adds 125 lines of code in 3
additional functions.

> 2. A similar to your proposition, but frames should be declared with a
> special PREFETCH opcode (with 2- or 4-bytes argument). Large data
> pickled outside frames (this prevents doublecopying).

No doublecopying is necessary (not in the C version, that is). That
said, this is an interesting idea.
Date User Action Args
2013-04-27 10:38:32pitrousetrecipients: + pitrou, rhettinger, alexandre.vassalotti, Arfrever, asvetlov, neologix, serhiy.storchaka
2013-04-27 10:38:32pitroulinkissue17810 messages
2013-04-27 10:38:31pitroucreate