Profiling with pprof

When an order-search endpoint feels slow or a worker's memory keeps climbing, guessing at the cause wastes hours and usually picks the wrong target. Go ships a profiler called pprof in the standard library, and it answers the question "where is the time and memory actually going?" with sampled stack traces you can read like a flame graph. This lesson covers the profile types pprof collects, the two ways to enable it (HTTP for long-running services, direct calls for one-shot tools and benchmarks), and how to read the output without getting lost.