go-profiler-notes
Hey there 👋🏻, I'm felixge and I've just started a new job at Datadog to work on Continuous Profiling for Go.
I found that Go has a lot of profilers and there are many tools for looking at the data, but that there is very little information on what any of it means. So in order to make sure that I know what I'm talking about, I've started to research the existing profilers and how they work. This repository is my attempt to summarize my findings in the hope that it might be useful to others.
External Links
- Go Docs
- Diagnostics: Has a very good overview over the available profiling and tracing facilities but doesn't go into a lot of depth.
- runtime/pprof: Lists the available profiles and has a little more explanation about what kind of data they produce.
- runtime: Has documentation on the various control knobs and pprof facilities, e.g.
MemProfileRate
. - net/http/pprof: Not a lot of docs, but diving into the code from there shows how the various profilers can be started/stopped on demand.
- JBD
- Profiler labels in Go: An introduction to using pprof labels and how they allow you to add additional context to your profiles.
- Custom pprof profiles: Example for using custom profiles, shows tracking open/close events of a blob store and how to figure out how many blobs are open at a given time.
- Mutex profile: Brief intro to the mutex profile.
- Using Instruments to profile Go programs: How to use the macOS Instruments app (I think it's built on dtrace) to profile Go programs. Not clear what the benfits are, if any.
- Profiling Go programs with pprof by Julia Evans: A nice tour with a focus on heap profiling and the pprof output format.
Got great links to recommend? Open an issue or PR, I'd happy to add your suggestions : ).
Stargazers over time
License
The markdown files in this repository are licensed under the CC BY-SA 4.0 license.
Disclaimers
I'm felixge and work at Datadog on Continuous Profiling for Go. You should check it out. We're also hiring : ).
The information on this page is believed to be correct, but no warranty is provided. Feedback is welcome!