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

fix: don't rely on std.time.microTimestamp() for accurate statistics #8

Merged
merged 1 commit into from
Mar 14, 2024

Conversation

robbielyman
Copy link
Contributor

I don't know the extent to which you care about accuracy for rendering statistics. I found when working on seamstress that the timestamp calls in std.time were so unreliable as to be unusable, sometimes reporting negative time deltas within a single
function. std.time.Timer, on the other hand, has been rock-solid in my experience.

I don't know the extent to which you care about accuracy for rendering
statistics. I found when working on seamstress that the `timestamp`
calls in `std.time` were so unreliable as to be unusable, sometimes
reporting negative time deltas within a single
function. `std.time.Timer`, on the other hand, has been rock-solid in
my experience.
@rockorager rockorager merged commit 9496270 into rockorager:main Mar 14, 2024
@rockorager
Copy link
Owner

Thanks! The stats don't need crazy accuracy, but I'll always take more accuracy if it doesn't cost much!

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

Successfully merging this pull request may close these issues.

2 participants