Author vstinner
Recipients josh.r, neologix, njs, pitrou, skrah, vstinner
Date 2014-04-16.08:06:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwZQCm87j9W8nrTFpXM_OonJabf_oCeQaefOT=nNKNbAEg@mail.gmail.com>
In-reply-to <CAH_1eM3TRmqR_0XU3mjvbZiAZcHyrw5cJ9KcvKCmYQjwVz_6zA@mail.gmail.com>
Content
2014-04-16 3:18 GMT-04:00 Charles-François Natali <report@bugs.python.org>:
>> It calls calloc(size) instead of malloc(size), calloc() which can be faster than malloc()+memset(), see:
>> https://mail.python.org/pipermail/python-dev/2014-April/133985.html
>
> It will only make a difference if the allocated region is large enough
> to be allocated by mmap (so not for 90% of objects).

Even if there are only 10% of cases where it may be faster, I think
that it's interesting to use calloc() to allocate Python objects. You
may create large Python objects ;-)

I didn't check which objects use (indirectly) _PyObject_GC_Calloc().
History
Date User Action Args
2014-04-16 08:06:13vstinnersetrecipients: + vstinner, pitrou, njs, skrah, neologix, josh.r
2014-04-16 08:06:13vstinnerlinkissue21233 messages
2014-04-16 08:06:13vstinnercreate