Message 370007 - Python tracker

➜

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	methane
Recipients	methane, pablogsal, pitrou, serhiy.storchaka, vstinner
Date	2020-05-26.15:56:46
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1590508606.57.0.597160879619.issue40781@roundup.psfhosted.org>
In-reply-to

Content
I use it often when I investigate memory usage. It provides some useful information even in release Python build. For example: * Which size class is most allocated? * How many block are allocated? * Which size class have most free blocks? (e.g. Inner fragmentation) * Combined with tracing application to stderr, which part of the application increase memory usage?

I use it often when I investigate memory usage.
It provides some useful information even in release Python build. For example:

* Which size class is most allocated?
* How many block are allocated?
* Which size class have most free blocks? (e.g. Inner fragmentation)
* Combined with tracing application to stderr, which part of the application increase memory usage?

History
Date	User	Action	Args
2020-05-26 15:56:46	methane	set	recipients: + methane, pitrou, vstinner, serhiy.storchaka, pablogsal
2020-05-26 15:56:46	methane	set	messageid: <1590508606.57.0.597160879619.issue40781@roundup.psfhosted.org>
2020-05-26 15:56:46	methane	link	issue40781 messages
2020-05-26 15:56:46	methane	create