Author vstinner
Recipients josh.r, jtaylor, neologix, njs, pitrou, skrah, vstinner
Date 2014-04-28.21:16:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwb288a+nFMMK1rS9tNu9AhXQPprnz1HdZtCepmGGZKHzg@mail.gmail.com>
In-reply-to <1398700337.7.0.783401118928.issue21233@psf.upfronthosting.co.za>
Content
> 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.
History
Date User Action Args
2014-04-28 21:16:01vstinnersetrecipients: + vstinner, pitrou, njs, skrah, neologix, jtaylor, josh.r
2014-04-28 21:16:00vstinnerlinkissue21233 messages
2014-04-28 21:16:00vstinnercreate