This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author steve.dower
Recipients paul.moore, steve.dower, tim.golden, vstinner, zach.ware
Date 2017-06-28.19:11:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1498677118.5.0.21408424274.issue26251@psf.upfronthosting.co.za>
In-reply-to
Content
We tried it at one point, but it made very little difference because we don't use the Windows heap for most allocations. IIRC, replacing Python's optimised allocator with the LFH was a slight performance regression, but I'm not sure the benchmarks were reliable enough back then to be trusted. I'm also not sure what optimisations have been performed in Windows 8/10.

Since the LFH is the default though, it really should just be a case of replacing Py_Malloc with a simple HeapAlloc shim and testing it. The APIs are nearly the same (the result of GetProcessHeap() will be stable for the lifetime of the process, and there's little value in creating specific heaps unless you intend to destroy it rather than free each allocation individually).
History
Date User Action Args
2017-06-28 19:11:58steve.dowersetrecipients: + steve.dower, paul.moore, vstinner, tim.golden, zach.ware
2017-06-28 19:11:58steve.dowersetmessageid: <1498677118.5.0.21408424274.issue26251@psf.upfronthosting.co.za>
2017-06-28 19:11:58steve.dowerlinkissue26251 messages
2017-06-28 19:11:58steve.dowercreate