March 12, 2026
Tiny stacks, big drama
Understanding the Go Runtime: The Scheduler
How Go juggles a million tiny tasks — and the crowd has thoughts
TLDR: The piece demystifies Go’s scheduler, the system that juggles countless tiny tasks on a few threads using a G-M-P trio. Commenters split between praise for deep dives and “you don’t need this to code,” while many turned it into a Kavya Joshi watch party for practical clarity and memes.
Go’s runtime just pulled back the curtain on its “scheduler,” the traffic cop that decides which tiny Go tasks (called goroutines) get to run on real computer threads. It’s built on a trio: G for goroutine (the work), M for machine (the thread), and P for processor (the permission slip to run). The community? They turned this into a watch party. Top comment linked straight to Kavya Joshi’s fan-favorite talks — Scheduler Saga and Understanding Channels — and suddenly the replies were all “class is in session.”
The strongest opinions split into two camps: one side calling the scheduler Go’s secret sauce that lets millions of tiny tasks fly, the other insisting “you don’t need to know any of this to ship code.” Cue the drama. Veterans teased that goroutines are “interns with 2KB backpacks,” while the runtime’s special manager mode (a housekeeping helper called g0) got crowned “the real boss.” Newcomers cheered the plain-English breakdown; purists rolled eyes at the hype and demanded benchmarks.
Jokes flew fast: “tiny stacks, big dreams,” “g0 is middle management,” and “without a P, your thread’s just loitering.” Bottom line: the article explained the magic; the comments turned it into a meme-fueled syllabus with a side of “do you really need to know this?” spice
Key Points
- •The Go scheduler multiplexes many goroutines onto a small number of OS threads to keep CPU cores busy and avoid starvation.
- •The scheduler relies on the GMP model: G (goroutine), M (OS thread), and P (processor).
- •A goroutine (G) is lightweight, with a small initial stack (~2KB) and saved registers, allowing pause and resume.
- •Each OS thread (M) has curg (current user goroutine) and g0 (a special runtime goroutine with a larger fixed stack, typically 16KB, possibly 32KB or 48KB).
- •An M must be attached to a P to run Go code; common operations like go statements, channel ops, and time.Sleep interact with the scheduler.