[Numpy-discussion] High-quality memory profiling for numpy in python 3.5 / volunteers needed

Julian Taylor jtaylor.debian at googlemail.com
Tue Apr 15 06:06:13 EDT 2014

> Good news, though! python-dev is in favor of adding calloc() to the
> core allocation interfaces, which will let numpy join the party. See
> python-dev thread:
>   https://mail.python.org/pipermail/python-dev/2014-April/133985.html
> It would be especially nice if we could get this into 3.5, since it
> seems likely that lots of numpy users will be switching to 3.5 when it
> comes out, and having a good memory tracing infrastructure there
> waiting for them make it even more awesome.
> Anyone interested in picking this up?
>   http://bugs.python.org/issue21233

I think it would be a better idea to instead of API functions for one
different type of allocator we get access to use the python hooks
directly with whatever allocator we want to use.
This would allow as to for example use aligned memory allocators which
might be relevant for the new cpu instruction sets with up to 64 byte
wide registers (it would be great if someone with avx512 hardware
could provide some benchmarks for unaligned, 16 byte aligned and 64
byte aligned memory to judge if this is actually required)

On the other hand memory tracing is a debugging feature and you might
not care about performance, so we could use the python allocators in
debug mode and the aligned unhooked allocators in normal mode?


More information about the NumPy-Discussion mailing list