Profiling Rust Applications

Profile Rust on Linux.md

Profiling performance

Using perf:

$ perf record -g binary
$ perf script | stackcollapse-perf.pl | rust-unmangle | flamegraph.pl > flame.svg

NOTE: See @GabrielMajeri's comments below about the -g option.

This requires you have flamegraph available in your path. The rust-unmangle script is optional but nice.

Also check out @dlaehnemann's more detailed walkthrough about generating flamegraphs here.

Profiling heap memory

Using valgrind (massif) and massif-visualiser:

$ valgrind --tool=massif binary

Also check out heaptrack, it's similar to massif but more useful out-of-the-box. It also has a nice gui experience:

$ heaptrack binary

Debugging

$ rust-gdb binary

Namespaces are prefixed by the crate name, which is probably also the name of the binary. You can do stuff like:

• break to set breakpoints
• print to print a variable
• step,next,finish to step through calls

Links

• http://blog.adamperry.me/rust/2016/07/24/profiling-rust-perf-flamegraph/
• https://llogiq.github.io/2015/07/15/profiling.html
• https://www.linux-apps.com/content/show.php?content=122409
• https://github.com/brendangregg/FlameGraph
• https://betterexplained.com/articles/debugging-with-gdb/

Thanks for the notice; you're right, now not even that is needed anymore. And thanks for your tutorial as well, the heaptrack_gui part was new to me!

Is there a similar thing for Windows?

Now, there is a cargo subcommand that can be used for flamegraphing Rust code. This should work cross-platform and a little less hacky than the solutions in these gists. Check it out here:
https://github.com/flamegraph-rs/flamegraph