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

eliminate excessive calls to mtime.Now() #2486

Merged
merged 2 commits into from
Apr 29, 2017
Merged

eliminate excessive calls to mtime.Now() #2486

merged 2 commits into from
Apr 29, 2017

Conversation

rade
Copy link
Member

@rade rade commented Apr 28, 2017

No description provided.

rade added 2 commits April 28, 2017 23:43
It is not used elsewhere and is rather specialised.
This isn't going to noticeably improve performance, but enables future
optimisations, e.g. more compact representations of LatestMaps where
many/all entries share the same timestamp.
@rade rade requested a review from ekimekim April 28, 2017 22:59
Copy link
Contributor

@ekimekim ekimekim left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Though shouldn't the performance gain be negligible since clock_gettime() doesn't do a full system call on most platforms?

@rade
Copy link
Member Author

rade commented Apr 29, 2017

Shouldn't the performance gain be negligible

I said that much in the commit message: "This isn't going to noticeably improve performance"

@rade rade merged commit b7eb53a into master Apr 29, 2017
@rade rade deleted the less-now branch July 5, 2017 13:09
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