You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
IOR miscalculates bandwidth when time drift is large #431
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?
Activity
JulianKunkel commentedon Aug 8, 2022
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?