homepage

> Hmm, obmalloc.c changed as well, so already the gcc optimizer can take
> different paths and produce different results.
If decimal depends on allocator performances, you should maybe try to
implement a freelist.
> Also I did set mpd_callocfunc to PyMem_Calloc().
I don't understand. 2% slowdown is when you use calloc? Do you have the
same speed if you don't use calloc? According to my benchmarks, calloc is
slower if some bytes are modified later.
> The bytes() speedup is very nice. Allocations that took one second
> are practically instant now.
Is it really useful? Who need bytes(10**8) object?
Faster creation of bytearray(int) may be useful in real applications. I
really like bytearray and memoryview to avoid memory copies.