flamegraph
Easy flamegraphs for Rust projects and everything else, without Perl or pipes <3 (by flamegraph-rs)
bytehound
A memory profiler for Linux. (by koute)
| flamegraph | bytehound | |
|---|---|---|
| 47 | 16 | |
| 4,262 | 3,856 | |
| 1.5% | - | |
| 7.4 | 3.8 | |
| 12 days ago | 9 months ago | |
| Rust | C | |
| Apache License 2.0 | GNU General Public License v3.0 or later |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
flamegraph
Posts with mentions or reviews of flamegraph.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-02-15.
-
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:
bytehound
Posts with mentions or reviews of bytehound.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-04-30.
-
My Rust program (Well, game) is leaking memory, 4MB/s.
I've found bytehound helpful for tracking memory leaks: https://github.com/koute/bytehound
-
Show HN: I wrote a tool in Rust for tracking all allocations in a Linux process
Interesting approach. How is performance compared to something like https://github.com/koute/bytehound
-
Introducing alloc-track: Precise memory profiling by stack trace and thread.
https://github.com/koute/bytehound is another tool in this space to be aware of
- Out of the loop: WASM for non-web projects
- Which gui crate would you suggest for a simple program?
-
Implementing a C++ memory allocator to track our framework memory usage
Ot sure if it will fit your needs but maybe bytehound is worth looking into.
-
Memory leak in a long running process.
I had a great success recently with https://github.com/koute/bytehound/issues/86
- Hi, I’m new in rust, I have some expirience with c# and its classes ans structs. I can’t find information about that is happend with struct in rust when I pass it to function argument. Are there some copy effect ?
- Does rust have a visual analysis tool for memory and performance like pprof of golang?
-
Memory freed but not immediately
Try using this: https://github.com/koute/bytehound
What are some alternatives?
When comparing flamegraph and bytehound you can also consider the following projects:
cargo-flamegraph - Easy flamegraphs for Rust projects and everything else, without Perl or pipes <3
memory-profiler - A memory profiler for Linux. [Moved to: https://github.com/koute/bytehound]
tracing - Application level tracing for Rust.
heaptrack - A heap memory profiler for Linux
tensorflow_macos - TensorFlow for macOS 11.0+ accelerated using Apple's ML Compute framework.
goawk - A POSIX-compliant AWK interpreter written in Go, with CSV support
hashbrown - Rust port of Google's SwissTable hash map
pprof - pprof is a tool for visualization and analysis of profiling data
heappy - heap profiler for rust
snmalloc-rs - rust bindings of snmalloc
pprof-rs - A Rust CPU profiler implemented with the help of backtrace-rs