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

Рет қаралды 7,308

Hypermode

Күн бұрын

Пікірлер: 20

@Rohinthas 3 ай бұрын

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

@Gigasharik5 Ай бұрын

absolute cinema

@rocknroll7967 7 ай бұрын

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

@RobertFletcherOBE 3 ай бұрын

This is really informative. Nice job

@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!

@larditard Жыл бұрын

This was a fantastic video, thank you!

@setkyarwalar 4 ай бұрын

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

@Fardin.Alizadeh Жыл бұрын

nice and concise!

@Rohinthas 4 ай бұрын

that was really helpful, thanks!

@andreypanin3096 2 ай бұрын

The animation is awesome, but the overall impression of the presentation is that it's a bit shallow. For example, aren't networking calls system calls? They are. How does a `g` gets unblocked after a syscall? By itself or with a help from the scheduler? Also, you said shrinking of a stack is easy, but if we borrowed a continuous region of memory from the heap, we can't simply ask the OS to reduce its size to match the new stack, can we?

@xv2beta999 28 күн бұрын

Networking calls are system calls, but if you use i.e net/http, go will manage these in a separate component net-poller, it is a interface, which is important, because the implementation of how net-poller will unblock a 'g' will depends on the actual O.S it is running.

@NguyenTuan-ek1pv 2 жыл бұрын

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

@chriszhang8365 2 жыл бұрын

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 2 жыл бұрын

@@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 10 ай бұрын

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

@bjj-and-cpp 7 ай бұрын

@@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)