Message259378
| Author |
vstinner |
| Recipients |
jtaylor, pitrou, rhettinger, serhiy.storchaka, vstinner, yselivanov |
| Date |
2016年02月02日.11:10:45 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1454411445.91.0.933604026266.issue26249@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> Hum, the point of PyMem_Malloc() is that it's distinct from PyObject_Malloc(), right? Why would you redirect one to the other?
For performances.
> (of course, we might question why we have two different families of allocation APIs...)
That's the real question: why does Python have PyMem family? Is it still justified in 2016?
--
Firefox uses jemalloc to limit the fragmentation of the heap memory. Once I spent a lot of time to try to understand the principle of fragmentation, and in my tiny benchmarks, jemalloc was *much* better than system allocator. By the way, jemalloc scales well on multiple threads ;-)
* http://www.canonware.com/jemalloc/
* https://github.com/jemalloc/jemalloc/wiki
My notes on heap memory fragmentation: http://haypo-notes.readthedocs.org/heap_fragmentation.html |
|