mirror of https://github.com/k3s-io/kubernetes.git synced 2026-01-05 23:47:50 +00:00

Files

Kubernetes Submit Queue 2b2af10a50 Merge pull request #41181 from tanshanshan/fix-wrong-shell

Automatic merge from submit-queue (batch tested with PRs 40917, 41181, 41123, 36592, 41183)

fix scheduler performance test script 

**What this PR does / why we need it**:

 

 `test-performance.sh` is  in  dir `kubernetes/test/integration/scheduler_perf`

the  dir `kubernetes/test/component/scheduler/perf`  does not exist

Thanks.

**Special notes for your reviewer**:

**Release note**:

```release-note
```

2017-02-09 23:10:44 -08:00

BUILD

move client/record

2017-01-31 19:14:13 -05:00

README.md

fix the wrong test path

2017-02-09 15:16:11 +08:00

scheduler_bench_test.go

…

scheduler_test.go

…

test-performance.sh

…

util.go

move client/record

2017-01-31 19:14:13 -05:00

README.md

Scheduler Performance Test

Motivation

We already have a performance testing system -- Kubemark. However, Kubemark requires setting up and bootstrapping a whole cluster, which takes a lot of time.

We want to have a standard way to reproduce scheduling latency metrics result and benchmark scheduler as simple and fast as possible. We have the following goals:

Save time on testing
- The test and benchmark can be run in a single box. We only set up components necessary to scheduling without booting up a cluster.
Profiling runtime metrics to find out bottleneck
- Write scheduler integration test but focus on performance measurement. Take advantage of go profiling tools and collect fine-grained metrics, like cpu-profiling, memory-profiling and block-profiling.
Reproduce test result easily
- We want to have a known place to do the performance related test for scheduler. Developers should just run one script to collect all the information they need.

Currently the test suite has the following:

density test (by adding a new Go test)
- schedule 30k pods on 1000 (fake) nodes and 3k pods on 100 (fake) nodes
- print out scheduling rate every second
- let you learn the rate changes vs number of scheduled pods
benchmark
- make use of go test -bench and report nanosecond/op.
- schedule b.N pods when the cluster has N nodes and P scheduled pods. Since it takes relatively long time to finish one round, b.N is small: 10 - 100.

How To Run

cd kubernetes/test/integration/scheduler_perf
./test-performance.sh