ceph-csi/vendor/k8s.io/kubernetes/test/integration/scheduler_perf
2018-07-31 14:53:26 +02:00
..
BUILD vendor update for CSI 0.3.0 2018-07-31 14:53:26 +02:00
main_test.go vendor files 2018-01-10 13:42:26 -05:00
OWNERS vendor files 2018-01-10 13:42:26 -05:00
README.md vendor files 2018-01-10 13:42:26 -05:00
scheduler_bench_test.go vendor updates 2018-03-07 11:43:06 -05:00
scheduler_perf_types.go vendor files 2018-01-10 13:42:26 -05:00
scheduler_test.go vendor update for CSI 0.3.0 2018-07-31 14:53:26 +02:00
test-performance.sh vendor files 2018-01-10 13:42:26 -05:00
util.go vendor update for CSI 0.3.0 2018-07-31 14:53:26 +02:00

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

# In Kubernetes root path
make generated_files

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

Analytics

Analytics