The Scheduler Saga - Kavya Joshi

Поделиться
HTML-код
  • Опубликовано: 12 дек 2024
  • НаукаНаука

Комментарии • 51

  • @andrewlaw1933
    @andrewlaw1933 2 года назад +27

    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
    @AmarjeetAnandsingh 5 лет назад +31

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

  • @blank001
    @blank001 Год назад +4

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

  • @arhyth
    @arhyth 5 лет назад +15

    great presenter. i love her older go channels talk.

  • @varshathkumarterli3694
    @varshathkumarterli3694 11 месяцев назад

    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.

  • @OfferoC
    @OfferoC 6 лет назад +8

    Awesome presentation. Thank you!

  • @sbef
    @sbef 7 месяцев назад

    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!

  • @aseemsavio6696
    @aseemsavio6696 2 года назад +1

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

  • @eoj096
    @eoj096 7 месяцев назад

    can't upvote this enough!

  • @nowarm
    @nowarm Год назад +1

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

  • @jeffliang166
    @jeffliang166 5 месяцев назад

    Amazing and well organized presentation! 👍

  • @ishnmu3113
    @ishnmu3113 Год назад

    Wow! Clean Presentation and Nicely explained. Thanks Kavya

  • @vladd3172
    @vladd3172 7 месяцев назад

    Awesome. Very good explained.

  • @alex_martishin
    @alex_martishin 11 месяцев назад

    Great talk! Very informative

  • @maheshkottapalli6945
    @maheshkottapalli6945 3 года назад +1

    Thank you a ton. Awesome presentation.

  • @robgreen13
    @robgreen13 5 лет назад +2

    Excellent content and presentation, thank you.

  • @alihussainkhan6976
    @alihussainkhan6976 3 месяца назад

    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

  • @cadenzah93
    @cadenzah93 3 года назад

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

  • @wodeqiangne
    @wodeqiangne 2 года назад

    nice presentation!personally i love her voice

  • @adipratapsinghaps
    @adipratapsinghaps 3 года назад

    Thanks, Kavya!

  • @tanchienhao
    @tanchienhao 8 месяцев назад

    Awesome talk

  • @jamshidiyr
    @jamshidiyr 4 месяца назад

    Thank you.

  • @abraham7966
    @abraham7966 4 года назад +1

    9:10 Welcome to Ruby.

  • @romankonovalov2588
    @romankonovalov2588 Год назад

    just the best

  • @yicai7
    @yicai7 Год назад

    Awesome!!!!

  • @asymptotion
    @asymptotion 4 года назад

    Great presentation!

  • @axea4554
    @axea4554 3 года назад

    Great presentation

  • @richardyang3963
    @richardyang3963 5 лет назад +2

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

    • @dune499
      @dune499 5 лет назад +1

      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
      @riankrishandi 3 года назад

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

    • @philipedekobi297
      @philipedekobi297 Год назад +1

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

    • @tarunpahuja3443
      @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.

  • @seriyanto
    @seriyanto 4 года назад +1

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

  • @byonggonchun3750
    @byonggonchun3750 3 года назад

    thanks kavya

  • @cs80211
    @cs80211 Год назад

    thanks

  • @jmcguckin
    @jmcguckin 11 месяцев назад

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

  • @allanguwatudde7623
    @allanguwatudde7623 Год назад

    nice talk

  • @nabromov
    @nabromov 3 года назад

    very useful!

  • @kamalabuhenamostafa
    @kamalabuhenamostafa 6 лет назад

    Stylic Presentation.

  • @欧阳楚-h4e
    @欧阳楚-h4e 4 года назад

    that is great!!!

  • @user-ov5nd1fb7s
    @user-ov5nd1fb7s 6 лет назад +2

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

    • @tarunpahuja3443
      @tarunpahuja3443 Год назад

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

    • @user-ov5nd1fb7s
      @user-ov5nd1fb7s Год назад

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

    • @tarunpahuja3443
      @tarunpahuja3443 Год назад

      Okay boss
      @@user-ov5nd1fb7s

  • @chengtaopan1676
    @chengtaopan1676 5 лет назад +1

    nothing further

  • @randydiffenderfer7793
    @randydiffenderfer7793 3 года назад

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

  • @andreypanin5257
    @andreypanin5257 5 лет назад

    Damn, she is trying so hard to sound mean!

  • @정지수-z6g
    @정지수-z6g 7 месяцев назад

    thanks kavya