Use ConcurrentSkipListMap for unconfirmed messages tracking#921
Draft
acogoluegnes wants to merge 1 commit into
Draft
Use ConcurrentSkipListMap for unconfirmed messages tracking#921acogoluegnes wants to merge 1 commit into
acogoluegnes wants to merge 1 commit into
Conversation
This eliminates TreeMap snapshot copies in the confirm timeout task. The monotonically increasing publishing IDs mean insertions always occur at the tail while removals (confirms) happen near the head, which suits the skip list's concurrent access patterns well.
acogoluegnes
force-pushed
the
unconfirmed-use-concurrent-skip-list-map
branch
from
efe4935 to
2d17cb8
Compare
acogoluegnes
changed the title
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This eliminates TreeMap snapshot copies in the confirm timeout task. The monotonically increasing publishing IDs mean insertions always occur at the tail while removals (confirms) happen near the head, which suits the skip list's concurrent access patterns well.