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 eitan.adler, methane, pitrou, serhiy.storchaka, vstinner, yselivanov
Date 2018-05-29.19:58:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Ok, I ran a subset of the benchmarks to record their memory footprint and got these results:

I'm not sure that the code tracking the memory usage in performance works :-) It may be worth to double check the code. By the way, perf has a --tracemalloc option, but performance doesn't have it.

perf has two options: --track-memory and --tracemalloc, see the doc:

perf has different implementations to track the memory usage:

* resource.getrusage(resource.RUSAGE_SELF) * 1024
* Windows: GetProcessMemoryInfo()
* tracemalloc: tracemalloc.get_traced_memory()[1]

In the 3 cases, perf saves the *peak* of the memory usage.
Date User Action Args
2018-05-29 19:58:11vstinnersetrecipients: + vstinner, pitrou, methane, serhiy.storchaka, yselivanov, eitan.adler
2018-05-29 19:58:11vstinnersetmessageid: <>
2018-05-29 19:58:11vstinnerlinkissue33597 messages
2018-05-29 19:58:11vstinnercreate