rbspy VS flamegraph

Even the most general profiler tool will show you each statement's accumulated time. These are called statistical profilers and give you a panoramic view of what the test is doing. An example of such a profiler is rbspy:

As a result, you need to craft a specific routine for each interpreter runtime (in some cases, each version of that runtime) to obtain symbol information. Educated eyes might have already noticed, it's not an easy undertaking considering the sheer amount of interpreted languages out there. For example, a very well known Ruby profiler, rbspy, generates code for reading internal structs of the Ruby runtime for each version.

I was a bit surprised to find out that the tool used to generate the flamegraph for Ruby (rbspy [1]) is written in Rust. lol

[1] https://github.com/rbspy/rbspy

c function is not very helpful to find the performance problem, so we dug deeper.

I don't see any obvious problems with your algorithm. I've had luck using cargo-flamegraph to identify the slow parts of my code. That's going to show you which parts to focus on improving the performance of!

From the readme of cargo flamegraph:

However, if your goal is to have the best performing code, you might want to take a look at profiling tools such as Cargo Flamegraph. They can show you where your code takes the most time and then you can try to make that part more efficient.

Better: an idea of how you can know where the bottleneck is. Use a profiler. cargo-flamegraph is nice.

I had some nice insights using FlameGraph that relies on Linux perf. There is a Rust version here.

Try doing a flamegraph to see where you are getting bottlenecked and post reaults here. https://github.com/flamegraph-rs/flamegraph

Use cargo-flamegraph and do a side-by-side with and without the panic?

Probably cargo flamegraph?

cargo install --git https://github.com/flamegraph-rs/flamegraph