Merged
Conversation
sveltos-agent memory usage has been optmized by re-using dynamic informer cache instead of direct API calls. Previously, sveltos-agent made direct API calls using a new discovery client and dynamic client for each fetch. This approach: - Fetched all resources with full managedFields and bypassed the informer cache entirely - Created new discovery clients repeatedly (expensive operation) - Resulted in high memory usage when fetching large numbers of resources Sveltos-agent code has been refactored to use the existing dynamic informer factory with transform functions: - Use informer cache when available - zero API calls, transforms already applied - Strip managedFields - in both code paths for consistency - Reuse cached REST mapper - avoid repeated discovery client creation
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.
sveltos-agent memory usage has been optmized by re-using dynamic informer cache instead of direct API calls.
Previously, sveltos-agent made direct API calls using a new discovery client and dynamic client for each fetch. This approach:
Sveltos-agent code has been refactored to use the existing dynamic informer factory with transform functions: