Distributed Systems 3.2: Clock synchronisation

Поділитися
Вставка
  • Опубліковано 5 вер 2024

КОМЕНТАРІ • 28

  • @meamea5127
    @meamea5127 3 роки тому +24

    What an amazing videos!! Thanks so much! I learn more in a 15-minute than my entire semester.

    • @Yaomuuuuu
      @Yaomuuuuu 2 роки тому +6

      what did u do in ur entire semester then。。。

    • @ihsannuruliman4005
      @ihsannuruliman4005 8 місяців тому

      @@Yaomuuuuu he's sleeping or being absent

  • @DeepalJayasekara
    @DeepalJayasekara 3 роки тому +5

    Thanks Dr. Kleppmann for the amazing series of lectures.

  • @ching-tangwang682
    @ching-tangwang682 Рік тому

    Thank you Dr. Kleppmann, you really make me get more interested in learning Distributed Systems. I've already bought your published book to study and learn more!

  • @gospojken
    @gospojken 2 роки тому +3

    This was extremely helpful and comprehensive. Thank you so much!

  • @mostinho7
    @mostinho7 Рік тому +1

    6:30 the total network delay can be found by looking at time stamps but this assumes network symmetry
    We can estimate what t4 was supposed to be and compare with actual. The estimate is t3+(delta/2). Difference between actual t4 and expected is the clock skew

  • @7xr1e20ln8
    @7xr1e20ln8 3 роки тому +2

    Thank you. NTP implementation was always like latin to me. But, i understand it much clearly now.

  • @joaofurukawa
    @joaofurukawa 2 місяці тому

    u are the GOAT of DS!

  • @kevinkaizhou
    @kevinkaizhou 3 роки тому +18

    Python: time.monotonic() to replace time.time()

    • @NitinSatish
      @NitinSatish 3 роки тому +2

      Thanks. I was wondering what the equivalent would be in Python

    • @MaxNRG
      @MaxNRG 3 роки тому +3

      time.monotonic_ns() → int
      Similar to monotonic(), but return time as nanoseconds.
      New in version 3.7.

  • @khaldrogo9451
    @khaldrogo9451 2 роки тому

    The frequency graph blew my mind. Wow.

  • @alexeiionov9812
    @alexeiionov9812 2 місяці тому

    so interesting! thank you so much for posting this series : )

  • @utsavseth7116
    @utsavseth7116 Рік тому

    Great work.

  • @outrospection4all
    @outrospection4all 3 роки тому +2

    @Martin, thanks for sharing. I'm new to this subject and trying to understand how to convert Time Error (drift in seconds per day) to precision in positioning. There are claims suggesting TE at 10^(-18) provides cm precision. If we multiply 10^(-18)*86400 (sec/day)*speed of light, the precision should sub cm. I would be grateful if you help with a comment or reference. Many thanks.

  • @mkgamesartvisuals
    @mkgamesartvisuals 2 роки тому

    Love it, thanks for sharing!

  • @naveenkothamasu
    @naveenkothamasu 2 роки тому

    I am thinking resetting the client clock happens if the skew is larger instead of slewing as in smaller skew case is because synchronizing the clocks would take a long time otherwise.

  • @AsemAmr19
    @AsemAmr19 Рік тому

    Thanks a lot for this video

  • @GooseBerry390
    @GooseBerry390 Рік тому

    I can't understand the slew chart at 10:06. If the clock ended being synchronized at ~200th mark (miilisecond?) itself, why was the quartz still ticking slowly until ~650 ms?

  • @donfeto7636
    @donfeto7636 6 місяців тому

    Thanks bro you legend

  • @jftsang
    @jftsang Рік тому

    In NTP why can you do (t4 - t1) - (t3 - t2) ? First two terms are from the client and second two terms are from the server, and if the two clocks have different rates than aren't you working with different units? Or is the assumption that the rates are 'close enough', i.e. corrections to the corrections are second-order?

  • @GooseBerry390
    @GooseBerry390 Рік тому

    Monotonic clocks are not affected by steps. But are they affected by slews?

  • @tomxu1761
    @tomxu1761 2 роки тому

    is the ntp used to sync the time for different timezone or in local network, because I see it accepts up to 1000s which is almost 30 minutes

    • @pashazzubuntu
      @pashazzubuntu 2 роки тому

      NTP has no concept of timezone, it's always UTC. The timezone is applied after sync

  • @ahemednor5201
    @ahemednor5201 2 роки тому

    🙏🌹🙏

  • @user-sk3yl6ib3m
    @user-sk3yl6ib3m 10 місяців тому

    icons are watching this video day before day exams

  • @ashutech1686
    @ashutech1686 3 роки тому

    I need java source code for Clock syncronization