Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Should choose ms/ns granularity for timestamp comparisons on-the-fly #16

Open
pnkfelix opened this issue Sep 5, 2017 · 0 comments
Open

Comments

@pnkfelix
Copy link
Owner

pnkfelix commented Sep 5, 2017

Spawned from #13 (comment)

Before running tango at all, do a local test of the host system to see if one can record nanosecond level deviations in the timestamps. (E.g. read the tango.stamp timestamp, add 1 nanosecond to it, re-stamp the file with that incremented value, re-read the new stamp, and see if its different from the value we first read.)

  • If we can record nanosecond level precision, then use nanosecond granularity when comparing timestamps of files.
  • If we can't record nanosecond level precision, then use millisecond granularity when comparing timestamps of files.

IMO it is not worth attempting to do this until after alexcrichton/filetime#9 is fixed.

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

1 participant