Go makes it deceptively easy to build scalable services — until production traffic exposes hidden bottlenecks. Latency spikes. Memory grows. Goroutines leak. CPU usage climbs. What is the runtime actually doing?

In this talk, we’ll walk through a realistic production incident and debug it using Go’s built-in tooling. We’ll explore Go’s memory model (stack vs heap, escape analysis), understand how the garbage collector behaves under load, and use pprof, flame graphs, and execution traces to identify CPU hotspots, memory pressure, and blocking patterns.

Beyond theory, we’ll apply fixes and measure their impact.

You’ll leave with a practical framework for diagnosing performance issues, tuning Go services confidently, and turning runtime insight into production-grade improvements.