4 articles
How to use Go's pprof toolchain to profile CPU, memory, goroutines, block, and mutex — collect profiles safely in production and act on what you find.
pprof tells you where CPU time went. trace tells you why goroutines weren't running. Both ship with Go. Here's how to pick the right one for your problem.
How Go's garbage collector works, what GOGC and GOMEMLIMIT actually control, how the Pacer schedules GC work, and how to tune these for your service.
How Go's append and map growth work, when pre-allocation actually helps, benchmark results across slice sizes, and practical rules for hot-path code.