Go execution tracer | Gopher Academy Blog
Introduction Ever wondered how are your goroutines being scheduled by the go runtime? Ever tried to understand why adding concurrency to your program has not given it better performance?
Go execution tracer | Gopher Academy Blog Gopher Academy Blog Share André Carvalho Dec 23, 2017 9 min read Go execution tracer Introduction Ever wondered how are your goroutines being scheduled by the go runtime? Ever tried to understand why adding concurrency to your program has not given it better performance? The go execution tracer can help answer these and other questions to help you diagnose performance issues, e.g, latency, contention and poor parallelization. The tool is available since go 1.5 and works by instrumenting the go runtime for specific events, such as: Creation, start and e
related reading
- Diagnostics - The Go Programming Languagego.dev
- Profiling Go programs with pprofjvns.ca
- Data Race Detector - The Go Programming Languagego.dev
- Notes on structured concurrency, or: Go statement considered harmful - njs blogvorpus.org
- All my favorite tracing tools: eBPF, QEMU, Perfetto, new ones I built and more - Tristan Humethume.ca
- Frequently Asked Questions (FAQ) - The Go Programming Languagego.dev
- The Go Memory Model - The Go Programming Languagego.dev
- OpenTelemetry: A Guide to Observability with Go | Blog | Luca Cavallinlucavall.in
- Memory Allocation in Go | Melatoninghiant3223.github.io
- [Java][Profiling] Async-profiler - manual by use cases | JVM/Java profiling and tuningkrzysztofslusarski.github.io
- Goroutines - Concurrent Programming in Goprogramiz.com
- A Guide to the Go Garbage Collector - The Go Programming Languagego.dev