Goroutines: Under the Hood | Vicki Niu | Go Systems Conf SF 2020

Go Systems Conf SF 2020: systemsconf.io
Note: The comments feature is disabled for this video. For the best experience, post your comments and questions for Vicki at discuss.dgraph.... The core Dgraph team lives on Discuss, and the typical response time is less than 30-mins. Thank you for understanding!
Goroutines: Under the Hood
Goroutines are a key part of Go’s powerful concurrency model, but what really happens when you kick off a goroutine? Vicki walks through what go func() really does, while noting some of the common pitfalls when working with goroutines.
✅ Follow Vicki
Twitter: / vickiniu
LinkedIn: / vickiniu
GitHub: github.com/vic...
✅ Follow us on social media for the latest updates!
Twitter: / dgraphlabs
LinkedIn: / dgraph-labs
Facebook: / dgraphlabs

[@Rohinthas]

This has become a regular refresher watch for me, the presentation style really works for me!

[@RobertFletcherOBE]

This is really informative. Nice job

[@setkyarwalar]

Thank you ကျေးဇူးတင်ပါတယ်။

[@myrachoantonio8832]

wow I must confess that thats was a little weird intro of how you spent your free time , but it got me thinking that - maybe thats how geniuses spend their free time - coz honestly this material is awesome thank you very much!

[@rocknroll7967]

Thank you so much Vicki ! I could not find any resource which explains go routines in detail

[@Rohinthas]

that was really helpful, thanks!

[@larditard]

This was a fantastic video, thank you!

[@Fardin.Alizadeh]

nice and concise!

[@NguyenTuan-ek1pv]

Hi, why does Goroutine needs an OS thread to run on? Can it run without OS thread? Thank you.

[@chriszhang8365]

All code needs to be put in cpu to run. Go routine is a higher level concept than OS thread. From low level to high level: CPU => Processes => OS Threads => go runtime => Goroutines

[@NguyenTuan-ek1pv]

@@chriszhang8365 so does goroutines stack and os stack has anything to do with each other I'm still confused how they are combined It's great if you can give me some references Thanks for your reply

[@esra_erimez]

@@chriszhang8365 The importance of this reply cannot be overstated.

[@bjj-and-cpp]

@@NguyenTuan-ek1pv The OS scheduler needs a stack for any thread that it is running. It is alot of memory though (like 2MB). The Go runtime scheduler also has a stack for every goroutine. But the scheduler keeps alot of the context for threads in the runtime memory, so that goroutine stacks are really small (like 2KB)

[@taintedmind3033]

i fell i love...

[@faeancestor]

strange comment

[@brinckau]

I fell in love with goroutines too, they are really great!

[@esra_erimez]

Creepy