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, pitrou, r.david.murray, sbt, tim.golden, tim.peters, vstinner, Пётр.Дёмин
Date 2013-10-15.08:33:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1381825981.34.0.474975429152.issue19246@psf.upfronthosting.co.za>
In-reply-to
Content
> Victor, please read your own link before posting:

Oh. I missed this part, that's why I didn't understand Tim's remark.

So the issue comes the Windows heap allocator. I don't see any obvious improvment that Python can do to improve the memory usage. I close the issue.

You have to modify your application to allocate objects differently, to limit manually the fragmentation of the heap. Another option, maybe more complex, is to create a subprocess to process data, and destroy the process to release the memory. multiprocessing helps to implement that.

I will maybe try jemalloc on Windows, but I prefer to open a new issue if I find something interesting.
History
Date User Action Args
2013-10-15 08:33:01vstinnersetrecipients: + vstinner, tim.peters, pitrou, tim.golden, r.david.murray, sbt, Esa.Peuha, Пётр.Дёмин
2013-10-15 08:33:01vstinnersetmessageid: <1381825981.34.0.474975429152.issue19246@psf.upfronthosting.co.za>
2013-10-15 08:33:01vstinnerlinkissue19246 messages
2013-10-15 08:33:01vstinnercreate