Re:The Performance Impact of C++'s `final` Keyword
by TylerE on Tuesday April 23, 2024 @03:21PM
(#40136062)
I mean sure, but I've never seen much in a flamegraph besides noise.
Re:The Performance Impact of C++'s `final` Keyword
by neonsunset on Tuesday April 23, 2024 @05:29PM
(#40137528)
My experience is complete opposite. You just need to construct a realistic load test for the code and the bottlenecks will stand out (more often than not).
Also there is learning curve to grouping and aggregating data.
JVM ecosystem has IntelliJ Idea profiler and similar advanced tools (AFAIK).
.NET has VS/Rider/dotnet-trace profilers (they are very detailed) to produce flamegraphs.
Then there are native profilers which can work with any AOT compiled language that produces canonically symbolicated binaries: Rust, C#/F#(AOT mode), Go, Swift, C++, etc.
For example, you can do `samply record ./some_binary`[0] and then explore multi-threaded flamegraph once completed (I use it to profile C#, it's more convenient than dotTrace for preliminary perf work and is usually more than sufficient).
[0] https://github.com/mstange/samply