Author vstinner
Recipients Yury.Selivanov, alecsandru.patrascu, catalin.manciu, jtaylor, pitrou, rhettinger, serhiy.storchaka, vstinner, yselivanov
Date 2016-03-09.17:27:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1457544429.76.0.750981770881.issue26249@psf.upfronthosting.co.za>
In-reply-to
Content
> I'm talking about the performance improvement in third-party libraries, not the performance improvement in CPython itself which can be addressed by replacing the internal API calls.

Oh ok. I don't know how to measure the performance of third-party libraries. I expect no speedup or a little speedup, but no slow-down.


> Do you think it's reasonable to risk breaking external libraries just
for a hypothetic "performance improvement"?

The question is if my change really breaks anything in practice. I'm testing some popular C extensions to prepare an answer. Early results is that developer use correctly the Python allocator API :-)

I disagree on the fact that my change breaks any API. The API doc is clear. For example, you must use PyMem_Free() on memory allocated by PyMem_Malloc(). If you use free(), it fails badly with Python compiled in debug mode.

My issue #26516 "Add PYTHONMALLOC env var and add support for malloc debug hooks in release mode" may help developers to validate their own application.

I suggest you to continue the discussion on python-dev for a wider audience. I will test a few more projects before replying on the python-dev thread.
History
Date User Action Args
2016-03-09 17:27:09vstinnersetrecipients: + vstinner, rhettinger, pitrou, Yury.Selivanov, jtaylor, serhiy.storchaka, yselivanov, alecsandru.patrascu, catalin.manciu
2016-03-09 17:27:09vstinnersetmessageid: <1457544429.76.0.750981770881.issue26249@psf.upfronthosting.co.za>
2016-03-09 17:27:09vstinnerlinkissue26249 messages
2016-03-09 17:27:09vstinnercreate