-
Notifications
You must be signed in to change notification settings - Fork 40k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make sure that performance dashboards work. #44003
Comments
In particular, there's a variable set for all CI e2e runs that tells you where to put files - (This variable is empty by default, so you'd need to handle that case appropriately.) |
I think there is already some issue for it (though I couldn't find it now). |
@gmarek is working on it now. |
Is this fixed? Both performance dashboards are still not working. |
/cc @vishh |
On our side (perfdash.k8s.io) everything's fine. |
Automatic merge from submit-queue (batch tested with PRs 47470, 47260, 47411, 46852, 46135) Logs node e2e perf data to standalone json files Fixes the node-dash-perf issue in #44003. - Move perf data types to `test/e2e/perftype/perftype.go` so that the node-perf-dash can depend on. - Logs the perf data to standalone json files so that node-perf-dash can consume it easily. A sample run of `ci-kubernetes-node-kubelet-benchmark` is at https://console.cloud.google.com/storage/browser/ygg-gke-dev-bucket/e2e-node-test/ci-kubernetes-node-kubelet-benchmark/1. The corresponding changes in node-perf-dash is at kubernetes-retired/contrib#2628. **Release note**: `None` /sig node /area node-e2e /assign @Random-Liu
http://node-perf-dash.k8s.io has been fixed. This can be closed. |
agreed, its working for me as well. |
Thanks @yguo0905 for fixing this! |
Perfect. Thanks a lot @yguo0905! |
Automatic merge from submit-queue (batch tested with PRs 47675, 48001) Encodes ReportPrefix into the generated metrics file names Ref: #44003 Adds the test prefix to be part of the name. Otherwise the same test case running on different images will override each other. Nothing needs to be changed at the node-perf-dash side. See test run at https://console.cloud.google.com/storage/browser/ygg-gke-dev-bucket/e2e-node-test/ci-kubernetes-node-kubelet-benchmark/10. **Release note**: ``` None ``` /sig node /area node-e2e /assign @Random-Liu
Now we have several performance tests:
All of them are using https://github.com/kubernetes/kubernetes/blob/master/test/e2e/framework/perf_util.go, and printing the benchmark metrics into the test result directly.
http://perf-dash.k8s.io/ and http://node-perf-dash.k8s.io/ parse the test output, get the benchmark metrics and generate the performance dashboard.
However, both dashboards are broken now, because:
kubernetes-e2e-gce-scalability
=>ci-kubernetes-e2e-gce-scalability
. However, the configuration in the dashboard is not changed https://github.com/kubernetes/contrib/blob/master/perfdash/config.go and https://github.com/kubernetes/contrib/blob/master/node-perf-dash/node-perf-dash-deployment.yaml.The whole logic is so brittle. We should generate a dedicated file for performance metrics, and let the dashboard consume the metrics file.
@dchen1107 @ixdy @krzyzacy @gmarek @wojtek-t
/cc @kubernetes/sig-scalability-misc @kubernetes/sig-node-bugs
The text was updated successfully, but these errors were encountered: