Skip to content
This repository has been archived by the owner on Jun 30, 2021. It is now read-only.

Consider switching timing to time.monotonic() #84

Open
icook opened this issue Sep 30, 2014 · 3 comments
Open

Consider switching timing to time.monotonic() #84

icook opened this issue Sep 30, 2014 · 3 comments

Comments

@icook
Copy link
Member

icook commented Sep 30, 2014

All timing currently relies on system clock. It would be better to use monotonic.

https://docs.python.org/3/library/time.html#time.monotonic

@ericecook
Copy link
Member

This requires Python 3 unless you want to use something like https://pypi.python.org/pypi/monotonic/

@icook
Copy link
Member Author

icook commented Jul 28, 2015

Yeah, it's mostly a pipe dream since I don't remember feeling good about the quality of that module. Ideally we would switch to Python3 with guv, but that would require a big rewrite in some places. There's not a great resolution for this, but it's consequences are pretty minor as long as ntpd is being run. Perhaps adding ntpd to the production recommendations list would be good.

@ericecook
Copy link
Member

Yea I hear that. Last time I looked at guv it was still a bit greener than I'd like, although it looks like dev work is ongoing

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

No branches or pull requests

2 participants