mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-08-09 20:17:41 +00:00
scheduler-perf: inject "benchmark" as name into JSON result filename
This is required because an empty name is no longer supported: the
perf-dashboard is run with --allow-parsers-matching-all-tests=false with causes
perfdash to skip current configuration for BenchmarkPerfResults as it does not
have name
set (4674704f45/perfdash/metrics-downloader.go (L165-L167)
).
The perf-dash config needs to be updated accordingly.
This commit is contained in:
parent
b9c7726046
commit
2db577a560
@ -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:
|
||||
|
@ -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)
|
||||
}
|
||||
}
|
||||
|
Loading…
Reference in New Issue
Block a user