kubernetes/minikube

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

Open

#4,622 创建于 2019年6月27日

在 GitHub 查看
 (5 评论) (3 反应) (0 负责人)Go (31,799 star) (5,222 fork)batch import
area/performancehelp wantedkind/featurelifecycle/frozenpriority/backlog

描述

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.

贡献者指南

技术栈
go
领域
performancedevopstesting
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
over 1 week
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Go programmingminikube internalsknowledge of virtualization driverse2e testing experience
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
40
研究方向
The issue requests a script to measure minikube start/stop/delete speed on different drivers (virtualbox, hyperkit, hyperv, none) and auto generate a driver performance.md file in /docs on each release. To begin, examine existing e2e tests in the minikube repository (e.g., integration tests under test/integration/) to understand the test harness and how they invoke minikube commands. The script should be similar to existing tests but focus on timing operations. Look at the CI configuration (e.g., in .github/workflows) to see how tests are run on different drivers. The deliverable is a script that can be integrated into the release process, potentially as a new CI job. Note that this is a complex feature that requires understanding of multiple drivers and the release pipeline.