GopherCon 2018: The Scheduler Saga - Kavya Joshi

[@andrewlaw1933]

This really is a great talk. I spent most of the 90s working with task schedulers, and have recently been playing with Go. I'd never seen any explanation of how Go does scheduling, but this talk makes things crystal clear, and maps nicely onto my experience. Kavya clearly knows her stuff, and tries to keep things interesting by changing intonation and using a little stagecraft, rather than letting viewers drift off to sleep. Nice work!

[@AmarjeetAnandsingh]

Absolutely amazing presentation. So organized... Thanks kavya for such a great content

[@arhyth]

great presenter. i love her older go channels talk.

[@blank001]

Great talk and explanation, I would definitely watch this again to get a better grasp, thanks Kavya for this awesome talk.

[@aseemsavio6696]

Amazing presentation! I was linked to this from Gophers Slack. I'm grateful for the guy who did that!

[@sbef]

I've been stuck looking to improve an M:N scheduler for my OS/language... found this video and it answers a TON of design and performance questions I had. (Work stealing run queues were the keyword I was looking for) Excellent talk, thanks a bunch!

[@keistzenon9593]

Amazing presentation, great pacing, learned a lot, thank you!

[@varshathkumarterli3694]

Not sure about you guys, But I'm a beginner and had to rewatch this presentation few times to understand it to the depth. Honestly the content is awesome.

[@eoj096]

can't upvote this enough!

[@OfferoC]

Awesome presentation. Thank you!

[@jeffliang166]

Amazing and well organized presentation! 👍

[@nowarm]

this is so awesome and easy to understand. Thank you for sharing!

[@alex_martishin]

Great talk! Very informative

[@jamshidiyr]

Thank you.

[@tanchienhao]

Awesome talk

[@ishnmu3113]

Wow! Clean Presentation and Nicely explained. Thanks Kavya

[@vladd3172]

Awesome. Very good explained.

[@romankonovalov2588]

just the best

[@axea4554]

Great presentation

[@yicai7]

Awesome!!!!

[@alihussainkhan6976]

Thanks for such an informative content ! Worth saving hours of googling 😀 Since we can create new threads for the goroutines waiting in the local runQ for threads which are blocked on a long running goroutine, as long as the number of goroutine running threads is

[@abraham7966]

9:10 Welcome to Ruby.

[@robgreen13]

Excellent content and presentation, thank you.

[@maheshkottapalli6945]

Thank you a ton. Awesome presentation.

[@wodeqiangne]

nice presentation!personally i love her voice

[@adipratapsinghaps]

Thanks, Kavya!

[@cadenzah93]

25:25 nice summary, better watch this few times more

[@richardyang3963]

On 24:22, what if the T1 wake up? there will be 3 threads, which beyond the limitation of CPU cores?

[@dune499]

It will not "wake up". It notifies the monitor thread when it's runnable(waiting in the parking). And when the go routine running thread count is less than core number (this can happen if Tmain or T2 has a syscall), the monitor thread will take it from parking and allocate it it's run queue.

[@riankrishandi]

@@dune499 T1 will not wake up? so how about the g1 inside it? how will it continue the goroutine execution?

[@philipedekobi297]

@@riankrishandi once the syscall unblocks, T1 will get parked

[@tarunpahuja3443]

​@@philipedekobi297 @tamjidahmed9872 But lets say if the g1 inside T1 is not yet finished, where would it be placed. T1 does not have any associated runqueue.

[@asymptotion]

Great presentation!

[@byonggonchun3750]

thanks kavya

[@jingjibunandong]

thanks

[@allanguwatudde7623]

nice talk

[@jmcguckin]

What about performing work stealing first from cores located on the same die so as to minimize cache misses…

[@ЕвгенийЩербина-л8т]

size of linux thread is 8MB, not 8KB?

[@seriyanto]

slices at speakerdeck.com/kavya719/the-scheduler-saga

[@nabromov]

very useful!

[@欧阳楚-h4e]

that is great!!!

[@kamalabuhenamostafa]

Stylic Presentation.

[@user-ov5nd1fb7s]

Nice talk but i still don't know how can you have 200k go routines, with this structure.

[@tarunpahuja3443]

If there are 10 cores, You can have 1000s go routines on each local distributed queue.

[@user-ov5nd1fb7s]

@@tarunpahuja3443 yea..I know. This comment is more than 4 years old.

[@tarunpahuja3443]

Okay boss @@user-ov5nd1fb7s

[@chengtaopan1676]

nothing further

[@randydiffenderfer7793]

cool -- solves (go) world hunger! :D

[@andreypanin5257]

Damn, she is trying so hard to sound mean!

[@정지수-z6g]

thanks kavya