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 vstinner
Recipients Esa.Peuha, brian.curtin, pitrou, r.david.murray, tim.golden, tim.peters, vstinner, Пётр.Дёмин
Date 2013-10-14.11:12:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwZzxat0KOeXUDgxyr8FNGncFTcD3zrK7ezTcH84YimX7w@mail.gmail.com>
In-reply-to <1381742620.43.0.119057862007.issue19246@psf.upfronthosting.co.za>
Content
Python uses an allocator called "pymalloc". For allocations smaller
than 512 bytes, it uses arenas of 256 KB. If you allocate many small
objects and later release most of them (but not all!), the memory is
fragmented. For allocations larger than 512 bytes, Python falls back
to malloc/free.

It was discussed to replace pymalloc with Windows Low Fragmented Heap allocator.
History
Date User Action Args
2013-10-14 11:12:37vstinnersetrecipients: + vstinner, tim.peters, pitrou, tim.golden, r.david.murray, brian.curtin, Esa.Peuha, Пётр.Дёмин
2013-10-14 11:12:37vstinnerlinkissue19246 messages
2013-10-14 11:12:37vstinnercreate