mirror of https://github.com/k3s-io/kubernetes.git synced 2025-10-25 10:00:53 +00:00

Files

Kubernetes Submit Queue fb5fbc944a Merge pull request #46117 from ravisantoshgudimetla/scheduler_perf_arch

Automatic merge from submit-queue (batch tested with PRs 49316, 46117, 49064, 48073, 49323)

Modular extensions for kube scheduler perf testing framework

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

**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #45973

**Special notes for your reviewer**:
It is not same as the existing one, the previous one has a single nodeaffinity key with multiple values. This one has multiple keys, values.

**Release note**:



```
NONE
```

2017-07-20 17:02:47 -07:00

BUILD

Build files generated

2017-07-19 00:29:05 -04:00

main_test.go

use testmain in integration tests

2017-07-12 17:34:55 -07:00

OWNERS

Add ownership for the future of scheduler_perf and kubemark

2017-05-24 10:17:50 -04:00

README.md

…

scheduler_bench_test.go

…

scheduler_perf_types.go

# This is a combination of 2 commits.

2017-07-19 00:28:40 -04:00

scheduler_test.go

# This is a combination of 2 commits.

2017-07-19 00:28:40 -04:00

test-performance.sh

…

util.go

Update factory.go informers to update equivalence cache

2017-07-18 23:55:01 +08: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