Skip to content
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

Minimizing cpu/memory usage during times of high resource churn #731

Open
TNonet opened this issue Feb 21, 2025 · 1 comment
Open

Minimizing cpu/memory usage during times of high resource churn #731

TNonet opened this issue Feb 21, 2025 · 1 comment
Labels
kind/feature New feature

Comments

@TNonet
Copy link

TNonet commented Feb 21, 2025

What would you like to be added?

Once in a while, in our K8s cluster, we see periods of high resource churn, which pushes lots of events to the cluster's clustersynchroManager resulting in large CPU spikes. What is the recommended way to ensure that this leader elected pod is able to handle the load?

  • Do I increase worker count? What is to high / too low?
  • Can we shard clustersynchroManager by resource uid so multiple pods can handle the work?
  • Can we prune how/which updates the clustersynchroManager watches / listens for? I see there is a feature to prune fields but can that be expands / made more dynamic to suit specific needs? https://clusterpedia.io/docs/features/prune-fields/

Why is this needed?

Given the single pod nature of clustersynchroManager, it is important to make sure the pod can handle the rate of updates needed to sync the cluster

@TNonet TNonet added the kind/feature New feature label Feb 21, 2025
@clusterpedia-bot
Copy link

Hi @TNonet,
Thanks for opening an issue!
We will look into it as soon as possible.

Details

Instructions for interacting with me using comments are available here.
If you have questions or suggestions related to my behavior, please file an issue against the gh-ci-bot repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature
Projects
None yet
Development

No branches or pull requests

2 participants