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 pitrou
Recipients eitan.adler, methane, pitrou, serhiy.storchaka, vstinner, yselivanov
Date 2018-05-29.20:04:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1527624247.82.0.682650639539.issue33597@psf.upfronthosting.co.za>
In-reply-to
Content
> I'm not sure that the code tracking the memory usage in performance works

Why wouldn't it?  It certainly gives believable numbers (see above).

And it seems to defer to your own "perf" tool anyway.

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

I don't think tracemalloc is a good tool to compare memory usage, as it comes with its own overhead.  Also it won't account for issues such as memory fragmentation.

> In the 3 cases, perf saves the *peak* of the memory usage.

Well, yes, that's the point, thank you.
History
Date User Action Args
2018-05-29 20:04:07pitrousetrecipients: + pitrou, vstinner, methane, serhiy.storchaka, yselivanov, eitan.adler
2018-05-29 20:04:07pitrousetmessageid: <1527624247.82.0.682650639539.issue33597@psf.upfronthosting.co.za>
2018-05-29 20:04:07pitroulinkissue33597 messages
2018-05-29 20:04:07pitroucreate