Message187500
| Author |
pitrou |
| Recipients |
alexandre.vassalotti, asvetlov, pitrou |
| Date |
2013年04月21日.11:27:37 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1366543657.42.0.133406683761.issue17810@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Thank you for reviving this :)
A couple of questions:
- why ADDITEM in addition to ADDITEMS? I don't think single-element sets are an important use case (as opposed to, say, single-element tuples)
- what is the purpose of STACK_GLOBAL? I would say memoization of common names but you pass memoize=False
> For example, I think Stefan's idea, which is not specified in the
> PEP, to eliminate PUT opcodes is interesting. His proposal was to
> emit an implicit PUT opcode after each object pickled and make the
> Pickler and Unpickler classes agree on the scheme.
Are the savings worth it?
I've tried pickletools.optimize() on two objects:
- a typical data dict (http.client.responses). The pickle length decreases from 1155 to 1063 (8% shrink); unpickling is faster by 4%.
- a Logger object (logging.getLogger("foobar"). The pickle length decreases from 427 to 389 (9% shrink); unpickling is faster by 2%. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2013年04月21日 11:27:37 | pitrou | set | recipients:
+ pitrou, alexandre.vassalotti, asvetlov |
| 2013年04月21日 11:27:37 | pitrou | set | messageid: <1366543657.42.0.133406683761.issue17810@psf.upfronthosting.co.za> |
| 2013年04月21日 11:27:37 | pitrou | link | issue17810 messages |
| 2013年04月21日 11:27:37 | pitrou | create |
|