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.

Sign up for GitHub

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

Jump to bottom

Generate performance metric for minikube start/stop/delete speed on different drivers #4622

Open
medyagh opened this issue Jun 27, 2019 · 4 comments
Open

Generate performance metric for minikube start/stop/delete speed on different drivers #4622

medyagh opened this issue Jun 27, 2019 · 4 comments
Labels
area/performance Performance related issues help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@medyagh
Copy link
Member

medyagh commented Jun 27, 2019 •
edited

it would be a great thing to have a script to run on each release, that does the following:

  • measure how long minikube start, start again ,stop , delete takes on each different drivers such as, virtualbox, hyperkit, hyperv and none.

the script should generate the a dirver_performance.md file in the /docs automatically on each release and purpose a PR.

The script could run as an integration test. the same way that our e2e tests run.
@medyagh medyagh added area/performance Performance related issues help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Jun 27, 2019
@medyagh medyagh changed the title Generate minikube start/stop/delete speed on different drivers Generate performance metric for minikube start/stop/delete speed on different drivers Jun 27, 2019
@tstromberg tstromberg added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Jul 16, 2019
@afbjorklund afbjorklund mentioned this issue Jul 23, 2019
Closed
@tstromberg tstromberg mentioned this issue Sep 20, 2019
Closed
@tstromberg tstromberg added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 20, 2019
@tstromberg
Copy link
Contributor

Probably won't touch this until later in Q1.

@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 16, 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 15, 2020
@sharifelgamal
Copy link
Collaborator

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Apr 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/performance Performance related issues help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@tstromberg @medyagh @k8s-ci-robot @sharifelgamal @fejta-bot