hotspot
flamegraph
hotspot | flamegraph | |
---|---|---|
16 | 47 | |
3,874 | 4,287 | |
1.4% | 2.1% | |
9.3 | 7.4 | |
2 days ago | 15 days ago | |
C++ | Rust | |
GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
hotspot
- Hotspot: A GUI for the Linux perf profiler
-
What is your favourite profiling tool for C++?
perf with Hotspot 👌
-
Profiling C code on an M1 mac
If you’re able to use perf on Linux, I would recommend hotspot for visualizing the results.
-
What is the problem with transfer speeds withing Dolphin?
I can recommend you using the https://github.com/KDAB/hotspot/ tool whenever you want to study performance.
-
Data-driven performance optimization with Rust and Miri
Every Linux C/C++/Rust developer should know about https://github.com/KDAB/hotspot. It's convenient and fast. I use it for Rust all the time, and it provides all of these features on the back of regular old `perf`.
-
How to interpret a flamegraph?
Flamegraphs alone aren't a full picture of what your application is doing, but it can give you hints as to where to look. Another tool I often use is Hotspot which can open the perf.data file and provide more options for filtering and digging into the gathered data beyond the single flamegraph.
-
Twenty Years of Valgrind
Ignore the command, it's just a placeholder to get meaningful values. The -d flag adds basic cache events, by adding another -d you also get load and load miss events for the dTLB, iTLB and L1i cache.
But as mentioned, you can instrument any event supported by your system. Including very obscure events such as uops_executed.cycles_ge_2_uops_exec (Cycles where at least 2 uops were executed per-thread) or frontend_retired.latency_ge_2_bubbles_ge_2 (Retired instructions that are fetched after an interval where the front-end had at least 2 bubble-slots for a period of 2 cycles which was not interrupted by a back-end stall).
You can also record data using perf-record(1) and inspect them using perf-report(1) or - my personal favorite - the Hotspot tool (https://github.com/KDAB/hotspot).
Sorry for hijacking the discussion a little, but I think perf is an awesome little tool and not as widely known as it should be. IMO, when using it as a profiler (perf-record), it is vastly superior to any language-specific built-in profiler. Unfortunately some languages (such as Python or Haskell) are not a good fit for profiling using perf instrumentation as their stack frame model does not quite map to the C model.
-
Linux Perf Examples
> [...] how Perf compares to vendor tools like vTune [...] ?
Regarding the hardware events that Perf can capture on x86, it has pretty much all of them. So it should be equivalent to vTune for all practical purposes.
The big difference is in the UI -- or absence thereof. Perf is a low-level tool and its output is mostly text files. There is a curses-based TUI for perf-report (and even gtk version, but it is essentially the same as the TUI, just using GTK2 widgets), but that's about it.
By contrast, vTune comes with a heavy (electron-based?) GUI and is quite helpful in guiding beginners, with many graphs and explanations.
Of course, one can (and is expected to) complement Perf with an assortment of tools that process its output for visualization. For example, the flamegraph [1] and heat map [2] tools described in the article. But also KDAB hotspot [3] or HPerf for a vTune-style perf-report.
[1] https://github.com/brendangregg/FlameGraph
[2] https://github.com/brendangregg/HeatMap
[3] https://github.com/KDAB/hotspot
[4] https://www.poirrier.ca/hperf/
-
Parsers that don't yet exist?
https://github.com/KDAB/hotspot might contain parsing code you could use as an example (other than perf script). It always accepts raw perf.data, and there doesn't seem to be a way to feed it the output of perf script, so it might be parsing it directly instead of calling perf script.
flamegraph
-
Rust Tooling: 8 tools that will increase your productivity
You can install cargo-flamegraph with cargo install flamegraph. There are some underlying requirements to be able to use cargo-flamegraph; you will want to take a look at the repo here to make sure you have the right dependencies.
-
Need help making sense of these benchmark results
I tried to diagnose the issue with flamegraph, but unfortunately the flamegraph didn't show anything beyond the next call for some reason
-
Why is my code so slow ? advent of code 2022, day 16 (basic graph stuff)
having some tools to identify slowness origins (flamegraph is one... but not sure it's the way to go)
-
why is my code so slow ? advent of code 2023, day 16 (basic graph stuff)
I'm currently implementing a solution for the first part of the day 16. It work but it is really slow... I'd like to : - understand why - having some tools to identify slowness origins (flamegraph is one... but not sure it's the way to go) - eventually have some clue/solution/idea - have general feedback on what in my "coding style" is not appropriate for rust (I come from java/kotlin/ts even if I've already coded a bit in c/c++) : for example I love iterator & sequence but i feel they are not really suited to overuse in rust (mostly because of async & result).
-
how expensive is an operation?
Use a profiler. Flamegraph is a good way to visualise profiler output. This lets you identify which functions are taking up a large amount of time - and hence helps you identify where to focus your optimisation efforts.
-
Slow Rust Redis
You tried trying to see what takes the most time under load via flames? https://github.com/flamegraph-rs/flamegraph
- making a virtual machine in rust
-
Need help with rust performance
Well, in cases like that the answer is straight forward, use a profiler like https://github.com/flamegraph-rs/flamegraph
-
superdiff - a way to find similar code blocks in projects (comments appreciated)
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!
-
Data-driven performance optimization with Rust and Miri
From the readme of cargo flamegraph:
What are some alternatives?
FlameGraph - Stack trace visualizer
cargo-flamegraph - Easy flamegraphs for Rust projects and everything else, without Perl or pipes <3
polkit-dumb-agent - a polkit agent in 145 lines of code, because polkit is dumb and none of the other agents worked
tracing - Application level tracing for Rust.
firestorm - A fast intrusive flamegraph
tensorflow_macos - TensorFlow for macOS 11.0+ accelerated using Apple's ML Compute framework.
gta5view - Open Source Snapmatic and Savegame viewer/editor for GTA V
hashbrown - Rust port of Google's SwissTable hash map
heaptrack - A heap memory profiler for Linux
optick-rs - Optick for Rust
snmalloc-rs - rust bindings of snmalloc