3 ms·
I'd say yes we are ready. gettimeofday() should never be used to measure time[1], but at least with a negative leap second it's monotonic. We'll just get some
by thomashabets2 3mo ago
I'd say yes we are ready. gettimeofday() should never be used to measure time[1], but at least with a negative leap second it's monotonic.
We'll just get some poorly coded stuff claim that an operation took 1100ms instead of 100ms. Not great, but not -900ms.
Well, I say that, but per my link here F5 load balancers at least used to keep track of TCP connections using gettimeofday. And it's annoying that libpcap delivers metadata in wallclock time.
[1] https://blog.habets.se/2010/09/gettimeofday-should-never-be-used-to-measure-time.html https://blog.habets.se/2010/09/gettimeofday-should-never-be-...
- happytoexplain 3mo ago> gettimeofday() should never be used to measure time And yet, even as somebody who has no idea what platform you're referring to, I can still guarantee you that gettimeofday() is used to measure time on that platform. This is how software works, unfortunately.
- thomashabets2 3mo agoAs per my linked blog post…
- ivanjermakov 3mo agoRelated: https://news.ycombinator.com/item?id=32548085 https://news.ycombinator.com/item?id=32548085