Is it possible to generate a terminal-based summary for peak memory usage table ?

[tvalentyn]

My current workflow is:

1. convert the bin output into html table via memray table
2. open the table in the browser
3. sort the rows by the size in decreasing order (two clicks).

Is possible to get the same info from the terminal? If not, would it make sense to file a feature request?

Thanks!

[pablogsal]

Have you seen https://bloomberg.github.io/memray/summary.html? Does this work for your use case?

[tvalentyn]

Thank you!

it trimmed the filenames too much, so the output was not usable.

Trimming from the beginning, instead of the end, would work better in this case as file name is more meaningful than the preceding path.

[tvalentyn]

I took a look once again at summary output, in a wider terminal, and the output doesn't show the leak that I am able to see in the table output, so I think as is the summary command doesn't work for my usecase.
In anycase, memray is beyond awesome and I owe to post a success story once I finish debugging.

[tvalentyn]

In one example, summary shows a table with only 6 rows, while the table output has 10k rows.

[pablogsal]

Right, notice that these tools show different information: memray table shows you every individual allocation (one by one) that is in the high watermark or the leak set, while memray summary shows you aggregated allocations by location. In memray summary the functions themselves are shown and not allocations. This means that if a function has a call tree of foo->bar->baz and baz allocates, we will show 3 rows, even if there is only one allocation. Another thing to consider is that we only show a limited number of rows in memray summary (that can be controlled via a command line parameter).

In any case, if you can give as a simple reproducer to take a look the difference between table and summary in your case, we can help you explain why one has 10k rows and the other 6.

[pablogsal]

Btw, in general, you may find memray flamegraph the most informative reporter, because this shows the same information in a more graphical format.