Finding and Fixing a 50,000 Goroutine Leak That Nearly Killed Production

0Sign in to vote or save

This site does not allow itself to be embedded. You can still read it on the original site — the toolbar below keeps your place in the directory.

Memory usage: 47GB. Response time: 32 seconds. Goroutines: 50,847. The story of debugging and fixing a massive goroutine leak in production.

Comments

Nothing yet. Say the first thing.