From the same author, Heaptrack to investigate memory usage is also very helpful: <a href="https://invent.kde.org/sdk/heaptrack/" rel="nofollow">https://invent.kde.org/sdk/heaptrack/</a>
Great tool that has been really helpful in helping me find unexpected bottlenecks in the codebases I've been working on.<p>It's easy to use, and pairs beautifully with the unintrusive perf tool, which makes the combination a joy to use.<p>And, if combined with a codebase opened in QtCreator, you can click on a hotspot in the flamegraph, and it will bring you automagically to the correct file and line in QtCreator, without any explicit linking required between the two programs. I discovered that feature accidentally, and the fact that it just worked seamlessly really impressed me. (Tested on a Debian-based Linux).<p>A big thanks to KDAB for making this tool available to us!
I primarily do macOS development work and use Instruments for profiling, but have been working on Linux a lot lately and Hotspot has been pulled out a lot over the last few weeks. Highly recommended.
I couldn't figure out how to use hotspot. I used speedscope instead:
<a href="https://www.speedscope.app/" rel="nofollow">https://www.speedscope.app/</a><p>Maybe I should check out hotspot again.
I'm on FreeBSD, so its a lot of overhead to check myself: But, does this have a source view like Vtune, that can attribute cycles / cache misses / etc, to a line of code? I see it has an assembly view..