Go teams can now see which functions use the most CPU and memory, and where goroutines wait, straight from production. Atatus Continuous Profiling for Go builds on the Go runtime's own profiler and runs with low overhead, so it can stay on all the time.
Read hotspots in flame graphs and method tables, compare profiles across releases to catch regressions after a deploy, and let Insights flag memory leaks and sudden spikes for you.
What Go profiling shows you
- CPU flame graphs: Find the most CPU-intensive functions in your Go services with flame graphs and a sortable method table.
- Memory allocation profiling: See allocated and in-use memory and objects per function to find leaks and reduce garbage collection pressure.
- Goroutine, lock and delay profiles: Inspect the state of every goroutine, spot goroutine leaks and measure time spent waiting on locks and synchronization.
- Compare releases: Tag profiles with a version and environment, then put a baseline next to a comparison to see which functions grew after a deploy.
- Insights: Memory leaks, sudden spikes, resource exhaustion and long-running CPU trends are flagged for you, with the service and profile type for each.
- Simple setup: Import go.atatus.com/agent/profiler and call profiler.Start at the top of main(). See the Go profiling docs.