{"action":"created","issue":{"url":"https://api.github.com/repos/ThomasHabets/monotonic_clock/issues/4","labels_url":"https://api.github.com/repos/ThomasHabets/monotonic_clock/issues/4/labels{/name}","comments_url":"https://api.github.com/repos/ThomasHabets/monotonic_clock/issues/4/comments","events_url":"https://api.github.com/repos/ThomasHabets/monotonic_clock/issues/4/events","html_url":"https://github.com/ThomasHabets/monotonic_clock/issues/4","id":104663857,"number":4,"title":"How long does it take to read the clock?","user":{"login":"Napoleon-BlownApart","id":6958677,"avatar_url":"https://avatars.githubusercontent.com/u/6958677?v=3","gravatar_id":"","url":"https://api.github.com/users/Napoleon-BlownApart","html_url":"https://github.com/Napoleon-BlownApart","followers_url":"https://api.github.com/users/Napoleon-BlownApart/followers","following_url":"https://api.github.com/users/Napoleon-BlownApart/following{/other_user}","gists_url":"https://api.github.com/users/Napoleon-BlownApart/gists{/gist_id}","starred_url":"https://api.github.com/users/Napoleon-BlownApart/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Napoleon-BlownApart/subscriptions","organizations_url":"https://api.github.com/users/Napoleon-BlownApart/orgs","repos_url":"https://api.github.com/users/Napoleon-BlownApart/repos","events_url":"https://api.github.com/users/Napoleon-BlownApart/events{/privacy}","received_events_url":"https://api.github.com/users/Napoleon-BlownApart/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-09-03T10:26:55Z","updated_at":"2015-12-27T10:57:48Z","closed_at":"2015-12-27T10:57:48Z","body":"Hi Thomas,\r\n\r\n  I'm looking for a way to measure elapsed times between events that occur at 40Hz +.\r\n  So I'm wondering if you might be able to give an indication of how long it takes to read the clock (ie when taking a sample)?\r\n\r\nCheers,\r\nNap."},"comment":{"url":"https://api.github.com/repos/ThomasHabets/monotonic_clock/issues/comments/167401305","html_url":"https://github.com/ThomasHabets/monotonic_clock/issues/4#issuecomment-167401305","issue_url":"https://api.github.com/repos/ThomasHabets/monotonic_clock/issues/4","id":167401305,"user":{"login":"Napoleon-BlownApart","id":6958677,"avatar_url":"https://avatars.githubusercontent.com/u/6958677?v=3","gravatar_id":"","url":"https://api.github.com/users/Napoleon-BlownApart","html_url":"https://github.com/Napoleon-BlownApart","followers_url":"https://api.github.com/users/Napoleon-BlownApart/followers","following_url":"https://api.github.com/users/Napoleon-BlownApart/following{/other_user}","gists_url":"https://api.github.com/users/Napoleon-BlownApart/gists{/gist_id}","starred_url":"https://api.github.com/users/Napoleon-BlownApart/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Napoleon-BlownApart/subscriptions","organizations_url":"https://api.github.com/users/Napoleon-BlownApart/orgs","repos_url":"https://api.github.com/users/Napoleon-BlownApart/repos","events_url":"https://api.github.com/users/Napoleon-BlownApart/events{/privacy}","received_events_url":"https://api.github.com/users/Napoleon-BlownApart/received_events","type":"User","site_admin":false},"created_at":"2015-12-27T10:57:48Z","updated_at":"2015-12-27T10:57:48Z","body":"Thanks guys, after studying how Thomas implement his library, I used feature macros to allow me to have a fallback strategy with the following priorities: clock_gettime(CLOCK_MONOTONIC_RAW) >> clock_gettime(CLOCK_MONOTONIC) >> gettimeofday().  It did the trick for what I needed.\r\n\r\nsitsofe, thanks for posting the links, I had a quick look at them and they will help me in the future I'm sure.\r\n"}}