heappy
memory-profiler
heappy | memory-profiler | |
---|---|---|
2 | 3 | |
21 | 2,115 | |
- | - | |
8.5 | 8.4 | |
4 days ago | over 2 years ago | |
Rust | C | |
Apache License 2.0 | 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.
heappy
-
Why Not Rust?
> But, for example, some runtime-related tools (most notably, heap profiling) are just absent — it’s hard to reflect on the runtime of the program if there’s no runtime!
Yeah; I felt that pain too.
I tried to write something to address some parts of the missing space. It's still in the early stages but you may be interested:
https://github.com/mkmik/heappy
-
Go 1.17 Is Released
I hate to be "that guy" too, but coming from somebody who really likes Rust and is using it more and more (also at $dayjob now) we must admit that Go tooling is one step ahead. CPU profiler, allocation and heap profiler, lock contention profiler. It all comes out of the box.
Yes you have cargo flamegraph for profiling locally and you now have pprof-rs to mimick Go's embedded pprof support. But allocation heap profiling is still something I struggle with.
I saw there was a pprof-rs PR with a heap profiler but there was some doubt as to whether it worked correctly; to get a feeling of how that approach would work but without having to fork pprof-rs I implemented the https://github.com/mkmik/heappy crate which I can use to produce memory allocation flamegraphs (using the same "go tool pprof" tooling!) in real code I run and figure out if it works in practice before pushing it upstream.
But stuff you give for granted like figuring out which structure accounts for most used memory, is very hard to achieve. The servo project uses an internal macro that help you trace the object sizes but it's hard to use outside the servo project.
The GC makes some things very easy, and it's not just about programmers not having to care about memory; it's also that the same reference tracing mechanism used to implement GC can be used to cheaply get profiling information.
memory-profiler
-
Go 1.17 Is Released
> But allocation heap profiling is still something I struggle with.
Have you tried this one? https://github.com/koute/memory-profiler
-
Is there a reliable way to find out where my memory is going?
I got very good results with https://github.com/koute/memory-profiler
- How to find a memory leak in a Rust program?
What are some alternatives?
bytehound - A memory profiler for Linux.
textot.rs - Text operational transform library, for rust. Compatible with libot, ottypes/text.
heaptrack - A heap memory profiler for Linux
dhat-rs - Heap profiling and ad hoc profiling for Rust programs.
goimports - [mirror] Go Tools
go - The Go programming language
goawk - A POSIX-compliant AWK interpreter written in Go, with CSV support