[host] windows: use millisecond precision for BootTime() #1397
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.
Previously, system uptime is truncated to seconds, and then the subtraction from
time.Now()
is performed. Because uptime does not roll over to the next second at the same instant astime.Now()
, thenBootTime()
ends up not being precise, and often varies by 1 second.This commit does the subtraction before truncating to seconds, which results in a significantly lower chance of variance in
BootTime()
.Old behaviour before change:
New behaviour after change:
Note that there is still a chance for
BootTime()
to roll over e.g. if the true boot time's milliseconds portion is close to 0. There is not much to be done about this since we cannot get bothGetTickCount
andtime.Now
atomically at the same instant.