[issue26251] Use "Low-fragmentation Heap" memory allocator on Windows

2018-05-29 Thread STINNER Victor
STINNER Victor added the comment: I failed to find the bandwidth to work on this issue since 2 years, so I just abandon this idea. However the performance benefit is non obvious. -- resolution: -> out of date stage: -> resolved status: open -> closed

[issue26251] Use "Low-fragmentation Heap" memory allocator on Windows

2017-07-03 Thread Steve Dower
Steve Dower added the comment: I wouldn't be opposed to seeing it tried again, but I have no strong opinion. I don't think this is a major performance bottleneck right now. -- ___ Python tracker

[issue26251] Use "Low-fragmentation Heap" memory allocator on Windows

2017-07-03 Thread STINNER Victor
STINNER Victor added the comment: Steve: "We tried it at one point, but it made very little difference (...)" Ok. Can I close the issue? -- ___ Python tracker

[issue26251] Use "Low-fragmentation Heap" memory allocator on Windows

2017-06-28 Thread Steve Dower
Steve Dower added the comment: 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

[issue26251] Use "Low-fragmentation Heap" memory allocator on Windows

2017-06-27 Thread STINNER Victor
STINNER Victor added the comment: Is there anyway interested to experiment to write such change and run benchmarks with it? -- ___ Python tracker ___

[issue26251] Use "Low-fragmentation Heap" memory allocator on Windows

2016-01-31 Thread STINNER Victor
STINNER Victor added the comment: The issue #19246 "high fragmentation of the memory heap on Windows" was rejected but discussed the Windows Low Fragmented Heap. -- ___ Python tracker

[issue26251] Use "Low-fragmentation Heap" memory allocator on Windows

2016-01-31 Thread STINNER Victor
STINNER Victor added the comment: "Low-fragmentation Heap": https://msdn.microsoft.com/en-us/library/windows/desktop/aa366750%28v=vs.85%29.aspx -- ___ Python tracker

[issue26251] Use "Low-fragmentation Heap" memory allocator on Windows

2016-01-31 Thread STINNER Victor
New submission from STINNER Victor: Python has a memory allocator optimized for allocations <= 512 bytes: PyObject_Malloc(). It was discussed to replace it by the native "Low-fragmentation Heap" memory allocator on Windows. I'm not aware of anyone who tried that. I would nice to try,