hotspot
crater
hotspot | crater | |
---|---|---|
16 | 23 | |
3,874 | 615 | |
1.4% | 2.3% | |
9.3 | 7.8 | |
2 days ago | about 1 month ago | |
C++ | Rust | |
GNU General Public License v3.0 or later | - |
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.
crater
-
Semver violations are common, better tooling is the answer
yup, they reference it as an inspiration: https://github.com/rust-lang/crater
it's probably impossible to automate an entire ecosystem, and there is value to enabling a tighter integration within a project ecosystem (a subset of the language ecosystem).
-
Trip Summer ISO C++ standards meeting (Varna, Bulgaria)
Rather than hypothesising about an imagined tool you could look at the actual tool which of course is in Rust's source code repo: https://github.com/rust-lang/crater
> new proposed C++ changes - are checked against only easily and "well-known" accessible package.
Now that I have, so to say, shown you mine, lets see yours. Where is the tool to perform these checks in C++?
-
GCC 13 and the state of gccrs
The "break things" part of "move fast" is not essential, Rust cares so much about breakage they literally compile and run the tests for every crate on crates.io and github using a tool called Crater. They do this just to test changes, even for stuff thats documented to be unstable, because thats just courtesy. And tooling makes it trivial to switch between Rust versions.
-
Do one thing, and do it well, or not.
The bot's named Crater if you want to look into it more.
-
Improving Rust compile times to enable adoption of memory safety
See https://github.com/rust-lang/crater
-
Discussion about the state of neovim's plugin ecosystem
Rust compiler developers use a tool called Crater to test potentially breaking compiler changes on all crates (Rust's name for libraries) uploaded to the official repository. If plugin stability is the issue, maybe a solution along these lines would be better than merging these plugins to Neovim's core?
-
Experienced C++ users: what do you like about Rust? How would you sell it to other C++ users?
https://github.com/rust-lang/crater is the bot they use to test proposed compiler/stdlib changes against slices of the crates.io library up to and including "all of it".
-
Data-driven performance optimization with Rust and Miri
The tool you're referring to is called Crater: https://github.com/rust-lang/crater.
- GHC 9.4.2 regresses being able to do math on aarch64
-
Rust for Linux officially merged
I'm pretty certain this isn't actually true. You should look at the editions, etc. Rust also has an insane guarantee which I am certain C/C++ don't offer: It rebuilds its entire library ecosystem each time it ships to make sure nothing breaks (https://crater.rust-lang.org). I've never seen an instance were old code didn't compile on a new compiler. Rust isn't forwards compatible (new code compiles on an old compiler) of course, but what is?
What are some alternatives?
FlameGraph - Stack trace visualizer
FluentValidation - A popular .NET validation library for building strongly-typed validation rules.
polkit-dumb-agent - a polkit agent in 145 lines of code, because polkit is dumb and none of the other agents worked
actix-net - A collection of lower-level libraries for composable network services.
firestorm - A fast intrusive flamegraph
Dapper - Dapper - a simple object mapper for .Net [Moved to: https://github.com/DapperLib/Dapper]
gta5view - Open Source Snapmatic and Savegame viewer/editor for GTA V
AutoMapper - A convention-based object-object mapper in .NET.
cargo-flamegraph - Easy flamegraphs for Rust projects and everything else, without Perl or pipes <3
rust-prehistory - historical archive of rust pre-publication development
optick-rs - Optick for Rust
NUnit - NUnit Framework