Reaching the ceiling of single-instance Go
summary
Examines limits of running a single Go process by measuring goroutine and defer counts, net/http concurrent connections, and garbage collector behavior. Uses recent Go performance improvements to quantify resource usage growth and identify when GC or other factors force you to scale beyond a single instance.
AI-written summary · about
chapters (12)
- 0:00Reaching the ceiling of single-instance Go
- 0:22Outline
- 0:37Intro - Motivation
- 1:55Challenges of Vertical Scaling
- 3:08Golang - Data
- 4:59Golang - Goroutines
- 8:35Golang - Defers
- 12:03Golang - net/http
- 13:47Golang - GC
- 16:01Golang - Channels
- 19:31Outro
- 20:27Questions?
related talks
56mThe Key to Go Efficiency is Just a Few Go Runtime Metrics Away!
34mGolang: Specific Performance Issues
30mMemory Management in Go: The good, the bad and the ugly
26mRespecting Memory Limits In Go
35mGo’s Trace Tooling and Concurrency
47mUnbounded Concurrency in Go
44mGo Profiling and Observability from Scratch
10mGo I made all the mistakes