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 | alexandre.vassalotti |
|---|---|
| Recipients | alexandre.vassalotti, habnabit, jcea, pitrou, schmir |
| Date | 2008年07月13日.20:26:23 |
| SpamBayes Score | 7.335834e-06 |
| Marked as misclassified | No |
| Message-id | <1215980786.64.0.61555501213.issue3119@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
On some benchmark of my own, I get a good 2x slowdown when this patch is applied. The benchmark consists of loading ~1.4 millions objects (mostly dict, list, str and int) from a pickle string. It is basically a torture test for the inner function calls overhead. Anyway, the slowdown doesn't bother me much. I think a "stackless" pickle module would be well appreciated by many Python users. There is a few things that stops me from applying this patch. First, the patch will break subclasses of Pickler that relies on the save() method (Although the method is an implementation detail that shouldn't used). Therefore, any patches that modifies the API of save() is straight out for 2.x. And for Python 3.0, your patch should also remove recursion from the _pickle module (the transparent C accelerator for pickle). |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年07月13日 20:26:27 | alexandre.vassalotti | set | spambayes_score: 7.33583e-06 -> 7.335834e-06 recipients: + alexandre.vassalotti, jcea, pitrou, schmir, habnabit |
| 2008年07月13日 20:26:26 | alexandre.vassalotti | set | spambayes_score: 7.33583e-06 -> 7.33583e-06 messageid: <1215980786.64.0.61555501213.issue3119@psf.upfronthosting.co.za> |
| 2008年07月13日 20:26:25 | alexandre.vassalotti | link | issue3119 messages |
| 2008年07月13日 20:26:24 | alexandre.vassalotti | create | |