Dmitry Vyukov — Go scheduler: Implementing language with lightweight concurrency

Hydra · 46K views · 2019 · 1:00:40

Open on YouTube

C, C++, Rust, Go & systems languagesCompilers, interpreters & program analysisSoftware performance & optimizationtalk

Why Hacker News recommends it

Recommended as a good watch on how Go's M:N:P scheduler works and why it was designed that way compared with alternative schemes.

What it is

Go runtime contributor Dmitry Vyukov looks inside the Go scheduler, explaining how goroutines and channels are implemented. He covers the main scheduler components and overall operation, then goes into details such as preemption and stacks.

Recommended by 2 HN commenters across 2 different months, 2020 to 2026.

What Hacker News said

Recommends RossBencina · 2020-02 · on “A Hitchhiker’s Guide to Asynchronous Programming”

I guess that's because they are "intros," and often multi-core event loops are implemented by the language runtime or some threadpool library. This is a good watch: Dmitry Vyukov — Go scheduler: Implementing language with lightweight concurrency (Oct 14, 2019) [this video]

Recommends c0balt · 2026-03 · on “Understanding the Go Runtime: The Scheduler”

[this video] - Dmitry Vyukov — Go scheduler: Implementing language with lightweight concurrency This one notably also explains the design considerations for golangs M:N:P in comparison to other schemes and which specific challenges it tries to address.

Cites lukaslalinsky · 2025-10 · on “How I turned Zig into my favorite language to write network programs in”

Go depends on the fact that it can track all pointers, and when it needs to resize stacks, it can update them. Previous versions of Go used segmented stacks, which are theoretically possible, if Zig really wanted (would need compiler support), but they have nasty performance side-effects, see [this video]