-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[Draft] Evict the longer time stamp subscription #37025
Open
DejinChen
wants to merge
1
commit into
project-chip:master
Choose a base branch
from
DejinChen:evict_longest_timerstamp_readhandler
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this the right logic? What is the actual behavior we are trying to implement?
If it's "evict the least newly created subscription", that's what the GetTransactionStartGeneration() thing above was trying to be a proxy for, but without adding new fields to ReadHandler, to avoid memory bloat. But if we are going to add new fields anyway, why wouldn't we just use those fields to track that information? But ideally we would not add fields.
If we really do want to evict handlers based on when they report, then this PR really needs to explain why that's a useful criterion, in the commit message or code comments (or maybe both).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe not the right logic.
GetTransactionStartGeneration
returns the generation recorded during the creation of the ReadHandler. If the least newly created subscription has the same generation and resource usage as others, it will be evicted when a new subscription is added. This pattern would repeat, with each subsequent new subscription causing the eviction of the least recently created one. As a result, only the least recently created subscription and those created before the handler became full would remain active until the generation updates. Is this the intended behavior?"There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The current logic evicts the oldest subscription that satisfies the other criteria, right?
The new code being added would evict the subscription that reported least recently, assuming things are all the same generation. But why is when a subscription reported a relevant thing at all?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes.
It has to report once receiving a new subscription.
Maybe we should try not to fill the ReadHandler instead of modifying the evict mechanism?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure what you mean by "try not to fill the ReadHandler"...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It means not to fill the ReadHandler pool in the InteractionModel.