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 Valentin.Lorentz, pitrou, tacocat, vstinner
Date 2016-11-29.16:13:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1480435981.36.0.812998475683.issue28663@psf.upfronthosting.co.za>
In-reply-to
Content
It's very hard to estimate the water high-mark for memory because the memory includes different things: read-only memory, mmap() on files, read-only memory pages shared between multiple processes for libraries, etc.

I suggest to use the tracemalloc module to have a better idea of the memory usage of the memory directly allocated by Python.
History
Date User Action Args
2016-11-29 16:13:01vstinnersetrecipients: + vstinner, pitrou, Valentin.Lorentz, tacocat
2016-11-29 16:13:01vstinnersetmessageid: <1480435981.36.0.812998475683.issue28663@psf.upfronthosting.co.za>
2016-11-29 16:13:01vstinnerlinkissue28663 messages
2016-11-29 16:13:01vstinnercreate