perf: Avoid many System.nanoTime calls in sharding passivation strategies #31834
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
patriknw
commented
Feb 10, 2023
patriknw
commented
- The recency based passivation strategies (new default) is calling System.nanoTime for each message.
- Add a ScheduledClock that updates the time once per second, but still increments time for subsequent calls
patriknw
force-pushed
the
wip-scheduled-clock-patriknw
branch
from
2915526 to
c68897e
Compare
…gies * The recency based passivation strategies (new default) is calling System.nanoTime for each message. * Add a ScheduledClock that updates the time once per second, but still increments time for subsequent calls
patriknw
force-pushed
the
wip-scheduled-clock-patriknw
branch
from
c68897e to
6137ea3
Compare
|
👍🏼 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.