Message106231
| Author |
matthiastroffaes |
| Recipients |
christian.heimes, gregory.p.smith, gvanrossum, loewis, matthiastroffaes, pitrou, r.david.murray, rhettinger |
| Date |
2010年05月21日.12:30:44 |
| SpamBayes Score |
2.6090924e-05 |
| Marked as misclassified |
No |
| Message-id |
<1274445047.21.0.894100309576.issue6695@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
I uploaded updates of the three relevant patches against the current revision of the py3k branch, as the old patches no longer applied cleanly due to whitespace changes.
To summarize:
* The first patch, py3k-rev81387-clearfreelist-dict_set_list.patch, simply adds freelist methods to the public API for dict, list, and set. No opposition has been expressed against this, so I hope this can be accepted.
* The second patch, py3k-rev81387-clearfreelist-gc_collect.patch, adds calls to these methods to gc.collect() - some opposition was expressed against the (already present before my patch!!) method of freeing lists during highest generation garbage collection. I attempted to measure the actual time spent on freeing the freelists in a simply python program which does a lot of allocation (attached as py3k-freelist_test.py). This apparently shows that clearing the freelists does not affect timing much at all.
* The third patch, file py3k-rev81387-clearfreelist-time_gc_collect.patch, causes estimates of the time spent on freeing the freelists to be printed to the console, and is obviously for testing/benchmarking purpose only.
* The tp_free_list patch is no longer relevant (see comment by Guido).
Hoping for a conclusion of this issue,
Matthias |
|