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

Reduce VM CPU overhead by 20% #5682

Closed
tstromberg opened this issue Oct 21, 2019 · 5 comments · Fixed by #8850
Closed

Reduce VM CPU overhead by 20% #5682

tstromberg opened this issue Oct 21, 2019 · 5 comments · Fixed by #8850
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Milestone

Comments

@tstromberg
Copy link
Contributor

Related to #3207 and #5398

#3207 can probably be closed - I don't believe we are at 50% usage any longer.

@tstromberg tstromberg added this to the v1.6.0-candidate milestone Oct 21, 2019
@tstromberg tstromberg modified the milestones: v1.6.0, v1.7.0-candidate Oct 30, 2019
@priyawadhwa priyawadhwa added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. kind/feature Categorizes issue or PR as related to a new feature. labels Nov 6, 2019
@priyawadhwa
Copy link

Running pidstat 1, I noticed that every 5 seconds the following command results in a high uptick in CPU usage (around 80%, from ~20%, for one core) on my linux machine:

/usr/local/bin/kubectl apply -f /etc/kubernetes/addons -l kubernetes.io/cluster-service!=true,addonmanager.kubernetes.io/mode=Reconcile --prune=true --prune-whitelist core/v1/ConfigMap --prune-whitelist core/v1/Endpoints --prune-whitelist core/v1/Namespace --prune-whitelist core/v1/PersistentVolumeClaim --prune-whitelist core/v1/PersistentVolume --prune-whitelist core/v1/Pod --prune-whitelist core/v1/ReplicationController --prune-whitelist core/v1/Secret --prune-whitelist core/v1/Service --prune-whitelist batch/v1/Job --prune-whitelist batch/v1beta1/CronJob --prune-whitelist apps/v1/DaemonSet --prune-whitelist apps/v1/Deployment --prune-whitelist apps/v1/ReplicaSet --prune-whitelist apps/v1/StatefulSet --prune-whitelist extensions/v1beta1/Ingress --recursive 

the addon manager currently polls every 5 seconds.

@tstromberg, WDYT of increasing polling time to 20 or 30 seconds? I have a graph showing CPU usage for the qemu process at 5 seconds and 20 seconds
for addon manager poll time.

@tstromberg tstromberg removed this from the v1.7.0-candidate milestone Dec 9, 2019
@tstromberg tstromberg added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Dec 9, 2019
@sharifelgamal
Copy link
Collaborator

This is being targeted for early next year.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 15, 2020
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 14, 2020
@priyawadhwa
Copy link

/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Apr 15, 2020
@priyawadhwa priyawadhwa added this to the v.1.12.0 milestone Jun 1, 2020
@medyagh medyagh modified the milestones: v.1.12.0-previous candidate (dumpster fire), v1.12.0-candidate Jun 1, 2020
@priyawadhwa priyawadhwa changed the title Reduce VM CPU overhead by 25% Reduce VM CPU overhead by 20% Jun 22, 2020
@medyagh medyagh modified the milestones: v1.12.0, v1.13.0-candidate Jul 8, 2020
howardjohn added a commit to howardjohn/istio that referenced this issue Mar 8, 2022
istio-testing pushed a commit to istio/istio that referenced this issue Mar 10, 2022
* Optimize single node kind cluster

Recommended by kubernetes/minikube#5682

* Update prow/config/default.yaml

Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>

Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
aryan16 pushed a commit to aryan16/istio that referenced this issue Mar 28, 2022
* Optimize single node kind cluster

Recommended by kubernetes/minikube#5682

* Update prow/config/default.yaml

Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>

Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
SRohitRaj pushed a commit to SRohitRaj/Istio that referenced this issue Jun 7, 2024
* Optimize single node kind cluster

Recommended by kubernetes/minikube#5682

* Update prow/config/default.yaml

Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>

Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants