Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm not sure why you
floor
the time diff.I would expect
string.format
to round the value properly. But since I can't seem to get any sub millisecond timestamps fromsocket.gettime
(on Windows), I have a hard time verifying it. For me, it appears to work fine to skipfloor
, and with Chronos, doing the above will reduce the displayed resolution.I also moved the "get time" call to before the memory formatting block. This reduces the measured time elapsed since the last message with about 0.0014ms. The lowest elapsed time between messages I get now is 0.0002ms.