wtf is cargo-profiler?

cargo-profiler is a tool for Rust developers who want to find out where their program is spending time or resources. Think of it as a speedometer and fuel gauge for your code. Instead of guessing which functions are slow or memory-hungry, you run one command and get a ranked breakdown showing exactly which parts of your code are doing the most work. Under the hood, it wraps two established Linux profiling tools called callgrind and cachegrind. You run a command like cargo profiler callgrind from within any Rust project, and the tool handles the setup. It feeds your compiled binary through the profiler, collects the raw data, and prints a clean summary showing the top functions by instruction count or cache misses. You can also point it at a specific binary directly, pass arguments to the program being profiled, limit the output to your top N functions, or sort by specific metrics. The audience is Rust developers working on Linux who need to optimize performance. For example, if you're building a matrix math library and your tests feel sluggish, this tool would show you that a specific kernel function accounts for forty percent of all instructions executed. That tells you exactly where to focus your optimization effort rather than hunting blindly. One notable limitation is that it only runs on Linux and requires a separate tool called valgrind to be installed first. The project also notes several features still on the roadmap, including the ability to compare two profiling runs side by side and support for additional profiling tools beyond callgrind and cachegrind.