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

Update to use ruby 2.1's access to the clock monotonic #22

Closed
copiousfreetime opened this issue May 9, 2014 · 4 comments
Closed

Update to use ruby 2.1's access to the clock monotonic #22

copiousfreetime opened this issue May 9, 2014 · 4 comments
Assignees

Comments

@copiousfreetime
Copy link
Owner

No description provided.

@copiousfreetime
Copy link
Owner Author

This may also require a conditional in the extconf to see if the clock monotonic access in ruby is available, if so then it should not have to run the extension

@ioquatix
Copy link

Is the monotonic clock the same as what Hitimes currently uses?

@copiousfreetime
Copy link
Owner Author

@ioquatix I think under the covers it might. I need to do some testing on windows to see what ruby on windows does, or if it is even available.

@copiousfreetime
Copy link
Owner Author

copiousfreetime commented Jun 15, 2018

Looks like under the covers ruby attempts to do the same thing I do, but out of the box it doesn't have the same resolution as I can get in hitimes. Ruby uses the same low level calls hitimes does, but uses the data a bit differently. For instance on OSX ruby only gives millisecond resolution while hitimes can give nanosecond - even though under the covers they both use mach_absolute_time

So, going to close this and not implement in terms of ruby's Process api since it doesn't appear to have the same functionality that hitimes has.

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

No branches or pull requests

2 participants