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 | lemburg |
|---|---|
| Recipients | amaury.forgeotdarc, jafo, lemburg, orivej, pitrou |
| Date | 2008年03月20日.19:10:33 |
| SpamBayes Score | 0.34565434 |
| Marked as misclassified | No |
| Message-id | <1206040234.4.0.995216977738.issue1943@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Regarding the benchmark: You can instrument a 2.x version of the interpreter to build the data set and then have the test load this data set in Py3k and have it replay the allocation/deallocation in the same way it was done on the 2.x system. I also expect that patch #2321 will have an effect on the performance since that patch changed the way memory allocation of the buffer was done (from using the system malloc() to using pymalloc's allocator for the buffer as well). |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年03月20日 19:10:34 | lemburg | set | spambayes_score: 0.345654 -> 0.34565434 recipients: + lemburg, jafo, amaury.forgeotdarc, pitrou, orivej |
| 2008年03月20日 19:10:34 | lemburg | set | spambayes_score: 0.345654 -> 0.345654 messageid: <1206040234.4.0.995216977738.issue1943@psf.upfronthosting.co.za> |
| 2008年03月20日 19:10:33 | lemburg | link | issue1943 messages |
| 2008年03月20日 19:10:33 | lemburg | create | |