go-profiler-notes
goimpl.nvim
| go-profiler-notes | goimpl.nvim | |
|---|---|---|
| 14 | 1 | |
| 3,483 | 48 | |
| 0.4% | - | |
| 1.5 | 1.2 | |
| about 2 months ago | 24 days ago | |
| Jupyter Notebook | Lua | |
| Creative Commons Attribution Share Alike 4.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.
go-profiler-notes
- The Busy Developer's Guide to Go Profiling, Tracing and Observability
-
Dwarf-Based Stack Walking Using eBPF
Thanks!
As @brancz mentioned, Delve uses DWARF unwind information to produce backtraces (they are stored in the .debug_frame section for Go).
You are right, Go enabled frame pointers for all architectures as of 1.17 [0]. This is enabled to allow profilers to work well, without having to use to techniques such as the one we describe in our post.
When it gets funny is that there's `gopclntab`, a 3rd option in Go to unwind stacks, used by `panic` and I believe other parts of the runtime. If you are interested in more details, Felix Geisendörfer's repo contains way more details [1]
[0]: https://go.dev/doc/go1.17
[1]: https://github.com/DataDog/go-profiler-notes/blob/main/stack...
- Resources to Learn Profiling and Benchmarking
- go-profiler-notes/README.md at main · DataDog/go-profiler-notes
- Fantastic Symbols and Where to Find Them - Part 1
-
Share your must-know Go development tips
this is a good read about pprof https://github.com/DataDog/go-profiler-notes/blob/main/guide/README.md
- The Busy Developers's Guide to Go Profiling, Tracing and Observability
goimpl.nvim
-
Share your must-know Go development tips
If you use telescope, I highly recommend goimpl telescope implementation. Rivals Goland's interface stub implementation. Great tool if you use a lot of interface.
What are some alternatives?
fgprof - 🚀 fgprof is a sampling Go profiler that allows you to analyze On-CPU as well as Off-CPU (e.g. I/O) time together.
vim-go - Go development plugin for Vim
parca - Continuous profiling for analysis of CPU and memory usage, down to the line number and throughout time. Saving infrastructure cost, improving performance, and increasing reliability.
gotests - Automatically generate Go test boilerplate from your source code.
parca-agent - eBPF based always-on profiler auto-discovering targets in Kubernetes and systemd, zero code changes or restarts needed!
thanos - Highly available Prometheus setup with long term storage capabilities. A CNCF Incubating project.
nvim
collect - collect all pprof profiles with one command
sqlc - Generate type-safe code from SQL
pics - File formats dissections and more...