STINNER Victor <vstin...@redhat.com> added the comment:
> 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: http://perf.readthedocs.io/en/latest/runner.html#misc 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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33597> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
