autoscaler
autoscaler copied to clipboard
how to delete the saved checkpoint.
i try to reinstall vpa and reinstall nginx.
but the vpa recommender is large form the beginning. i have set cpu-histogram-decay-half-life=1s in recommender-deployment.yaml and wait for one day , but the recommender is not became small.
how to delete the saved checkpoint ? i want to run vpa with a small recommender
I don't want the recommendation value to be consistently high. but now when the recommendation value become large. it will not be small when the pod cpu usage is small. i have already set cpu-histogram-decay-half-life=1s. but the recommendation value can not be smaller . do you have some suggesstions about it?
Best Lisa
Hi,
did you try somewhat larger values of the cpu-histogram-decay-half-life flag? I'd recommend setting for example 10 minutes and seeing if that behaves more like what you want. Sample decay is implemented by multiplying weight of new sample by 2n, where n is number of cpu-histogram-decay-half-life elapsed since the previous sample (+handling for when this multiplier gets too high).
So with cpu-histogram-decay-half-life=1s we'll be increasing weights 260. I suspect this might break the sample decay mechanism.
@shixinlishixinli if your concern is resolved can we close this issue?
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
I'm Closing this issue, as there is no response. Please reopen it again if you still have any concerns.
/close
@Shubham82: Closing this issue.
In response to this:
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.