[issue11849] glibc allocator doesn't release all free()ed memory

Antoine Pitrou report at bugs.python.org
Fri Nov 25 01:52:33 CET 2011


Antoine Pitrou <pitrou at free.fr> added the comment:

More surprising is that, even ignoring the allocation cost, other operations on the memory area seem more expensive:

$ ./python -m timeit -s "b=bytearray(500000)" "b[:] = b"
-> python 3.3:
1000 loops, best of 3: 367 usec per loop
-> python 3.2:
10000 loops, best of 3: 185 usec per loop

(note how this is just a dump memcpy)

----------

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


More information about the Python-bugs-list mailing list