Dmitry Vyukov — Go scheduler: Implementing language with lightweight concurrency

Channel:Hydra · Length:1:00:39 · Published:2019-10-14 · Views:47037

Watch on YouTube

Summary

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.

Why HN 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.

This one notably also explains the design considerations for golangs M:N:P in comparison to other schemes — HN, 2026

C, C++, Rust, Go & systems languages · Software performance & optimization · Compilers, interpreters & program analysis

Subtitles (excerpt)

hello my name is nithya view cough I work a software engineer at Google and today I will try to not you let fall asleep after the lunch by presenting the talk go scheduler implementing language was lightweight concurrency so I will talk about how to build a scheduler how to make it efficient and scalable and then I will talk about fairness stacks and preemption so this is about the go language go language has built-in support for concurrency and the main primitive for concurrency is called a goroutine logically goroutine is a thread of execution so logically it's the same as operating system threat and equality in our green fret and most material in this presentation is somewhat generic and a large degree applicable to operating system schedulers co-routine schedulers other languages hopefully if you find it interesting and useful even if you don't have specific interests in the go language but there are some go specifics first of all I am going to talk about what is currently implemented in the go language not about something else and the second go language imposes on us some requirements and constraints and we make our design decisions based on those requirements so if you will have some different

On Hacker News

[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. — c0balt, 2026-03
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) [VIDEO] — RossBencina, 2020-02
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 [VIDEO] — lukaslalinsky, 2025-10

Related videos