koord-yarn-operator: add cache filter in Manager to reduce memory occupied by the koord-yarn-operator. #90
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
added 2 commits
October 28, 2024 16:56
Signed-off-by: wangyang60 <wangy9834@163.com>
…ord-yarn-operator. Signed-off-by: wangyang60 <wangy9834@163.com>
|
PTAL @zwzhang0107 |
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.
Ⅰ. Describe what this PR does
When we used yarn-operator internally for yarn mixing, we found that the yarn-operator component took up a lot of memory. Through pprof inspection, we found that
ListAndWatchtook up a lot of memory. Finally, we found that the reason was thefield index. Therefore, we modified the default Cache so that thefield indexonly focuses on the NMpod of interest.before:
after:
Ⅱ. Does this pull request fix one issue?
Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews
V. Checklist
make test