How to monitor crate library size and memory footprint?


#1

I’m wondering what methods various projects use for monitoring the binary size of a library, as well as its runtime memory footprint, of the crates in heavy development.

For the binary size, currently I look at the size of target/release/*.rlib.

For runtime memory footprint, I don’t have a solution yet, but I think it could be an optional part of cargo bench, or a third-party cargo command to use existing tests/benches crates to monitor.

What do you think?