use unixNanoTime instead of time.Time in lockRequestorInfo #20140
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.
Community Contribution License
All community contributions in this pull request are licensed to the project maintainers
under the terms of the Apache 2 license.
By creating this pull request I represent that I have the right to license the
contributions to the project maintainers under the Apache 2 license.
Description
use unixNanoTime instead of time.Time in lockRequestorInfo
Motivation and Context
Bonus: Skip Source and Quorum fields in lockArgs that are
never sent during Unlock() phase.
How to test this PR?
This is mainly a data structure optimization to reduce
the size of the message from a few bytes, while these are
It is probably a bit over the top in general scenarios; there
are precise situations where the amount of locks and unlocks
held at high concurrency can become a problem for map
based lockers when their inherent runtime memory adds
latency.
Types of changes
Checklist:
commit-id
orPR #
here)