Resolving Go Application Performance Issues: CPU Usage and Memory Leaks with pprof and Flame Graphs
Introduction to Golang Profiling with pprof Profiling Go applications is not just a...
Tag archive
Introduction to Golang Profiling with pprof Profiling Go applications is not just a...
🔧 The Problem Every Go dev has heard "goroutines are cheap." True, relative to OS threads....

I built Peacock, a terminal JSON log viewer in Go, and it could not keep up with a busy log stream....

A parked goroutine burns zero CPU, so flame graphs miss leaks entirely. Read goroutine.pprof, set a NumGoroutine baseline, and gate CI with goleak.
Postmortem: Debugging a Go 1.23 Deadlock with pprof 1.3 and Grafana 10.4 (2026) Published:...
Most performance advice for Go is ritual — 'use sync.Pool,' 'avoid interface boxing,' 'preallocate slices.' Useful sometimes, hollow often. A production engineer's guide to profiling Go systems with pprof, reading escape analysis output, and understanding when the compiler actually inlines.
\n For long-running Go services handling 100k+ requests per second, garbage collection (GC) pause...
A post by ANKUSH CHOUDHARY JOHAL

In the world of high-concurrency systems, throwing more hardware at a problem is often the most...
In this post, I want to guide you through the whole process of profiling and benchmarking the...

This article is from bmf-tech.com - Goで始めるコードのパフォーマンス改善. Day 9 of Makuake Advent Calendar 2022! ...

This post reviews how I found a memory leak, how I fixed it, how I fixed similar issues in Google's...