Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Consider using nanotime() rather than currentMillis() #62

Open
nicost opened this issue Jan 14, 2023 · 1 comment
Open

Consider using nanotime() rather than currentMillis() #62

nicost opened this issue Jan 14, 2023 · 1 comment

Comments

@nicost
Copy link
Member

nicost commented Jan 14, 2023

Nanotime() is guaranteed monotonic, and has a much higher resolution than currentTimeMillis(). See: http://pzemtsov.github.io/2017/07/23/the-slow-currenttimemillis.html

@henrypinkard
Copy link
Member

Im all for it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants