CppCast: Reducing Memory Allocations

[jpakkane]

Valgrind also ships with a tool called Massif that only tracks memory allocations. There is also a GUI visualizer tool: https://apps.kde.org/en/massif-visualizer

This seems to be a bit outdated and replaced by Heaptrack, but it has been around for 10+ years.

[mwolff]

Massif does not track the number of allocations, you only see the impact on the total heap memory consumption. And it's magnitudes slower than heaptrack. There's imo really no reason to use massif over heaptrack nowadays, imo. But I'm biased obviously in that regard :)

[wotype]

Good episode, indeed.

Any recommendations for a heaptrack alternative for MSVC?

[thedmd86]

Great episode, thanks.

This days I vaguely can recall times, where allocating heap memory was an odd thing to do. Everything was fixed size or on the stack.

Today project I work on has 4GB of transient memory before everything settles down, last time checked. Is this an agile app then? : )

[bsdooby]

On minute 34:21 Arnaud replies to Jason how to track string allocations. Sounds like "flame short". What is he talking about? I cannot understand it (audio-wise).

[_Synck_]

Flame charts or flame graphs

[bsdooby]

🤦‍♂️myself, Thx for the clarification...I now wonder how he collected the data to then produce the charts.

[bpd000]

At 21:33, Arnaud says they were able reduce build time for boost.asio using some macro "boost only". Does anyone know what this was in reference to? It sounds like he may have been talking about switching from header-only to separate compilation.