github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-08-10 12:32:03 +00:00
Code Issues Projects Releases Wiki Activity

Merge pull request #118164 from pohly/scheduler_perf_results

Browse Source 
scheduler-perf: inject "benchmark" as name into JSON result filename
This commit is contained in:
Kubernetes Prow Robot 2023-05-22 00:06:20 -07:00 committed by GitHub
commit 3903a7e1f0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
test/integration/scheduler_perf/README.md
View File

@ -48,7 +48,7 @@ as "fast":
make test-integration WHAT=./test/integration/scheduler_perf ETCD_LOGLEVEL=warn KUBE_TEST_VMODULE="''" KUBE_TEST_ARGS="-run=^$$ -benchtime=1ns -bench=BenchmarkPerfScheduling -perf-scheduling-label-filter=performance,-fast"
```
Once the benchmark is finished, JSON file with metrics is available in the current directory (test/integration/scheduler_perf). Look for `BenchmarkPerfScheduling_YYYY-MM-DDTHH:MM:SSZ.json`.
Once the benchmark is finished, JSON file with metrics is available in the current directory (test/integration/scheduler_perf). Look for `BenchmarkPerfScheduling_benchmark_YYYY-MM-DDTHH:MM:SSZ.json`.
You can use `-data-items-dir` to generate the metrics file elsewhere.
In case you want to run a specific test in the suite, you can specify the test through `-bench` flag:

2
test/integration/scheduler_perf/scheduler_perf_test.go
View File

@ -724,7 +724,7 @@ func BenchmarkPerfScheduling(b *testing.B) {
}
})
}
if err := dataItems2JSONFile(dataItems, b.Name()); err != nil {
if err := dataItems2JSONFile(dataItems, b.Name()+"_benchmark"); err != nil {
b.Fatalf("unable to write measured data %+v: %v", dataItems, err)
}
}