Skip to content

IOR miscalculates bandwidth when time drift is large #431

Open

Description

@richard-mansfield

IOR miscalculates bandwidth if one or more compute nodes has a significant time drift.

IOR should either exit gracefully in this circumstance or use Lamport timestamp to synchronized thread timings.

Activity

  1. JulianKunkel commented on Aug 8, 2022

    @JulianKunkel
    Collaborator

    I do not believe that this is an IOR issue. Algorithmic-wise a detection of regular time drifts due to too fast/slow clocks is possible, however, there are unsteady ones too and I do not know any algorithm that can reliably deal with any type of clock errors - except if one constantly watches for time issues. However, any benchmark will have a similar challenge. Time synchronisation is something important for logs incl. security, so I believe there is no need to fix this unpleasantry but rather ensure that nodes have the right timing e.g. using NTP. Maybe there is a good reason not to time sync the nodes, though?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions