[issue26382] List object memory allocator

Catalin Gabriel Manciu report at bugs.python.org
Fri Feb 19 06:06:31 EST 2016


Catalin Gabriel Manciu added the comment:

Theoretically, an object type that consistently allocates more than the small object threshold would perform a bit slower because
it would first jump to the small object allocator, do the size comparison and then jump to malloc. There would be a small overhead 
if PyMem_* would be redirected to PyObject_* in this (hypothetical) case and the initial choice of PyMem_* over PyObject_* might have 
been determined by knowing about that overhead. This is because many think of PyMem_* as the lower-level allocator, PyObject_* as a
higher-level one. Of course, PyMem_Raw* should be used in such cases, but it's not as widely adopted as the other two.

I will post some benchmark results on your issue page as soon as I get them.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26382>
_______________________________________


More information about the Python-bugs-list mailing list