e2e-benchmarking
e2e-benchmarking copied to clipboard
cloud-bulldozer
Performance Tests for end Platforms
### Description updating for metrics added in [PR # 308](https://github.com/openshift-qe/ocp-qe-perfscale-ci/pull/308) and aws s3 storage metric.
OCM server consists of cluster service and account manager service. During ocm load testing we monitor metrics from both these services. In this change, kube-burner pulls metrics from ocm prometheus...
Signed-off-by: Sai Sindhur Malleni ### Description ### Fixes
When running the node-density* workloads of kube-burner, if I specify a NODE_COUNT that is smaller than the number of available workers, that test parameter value is not indexed. Instead, the...
After [PR](https://github.com/cloud-bulldozer/e2e-benchmarking/pull/474) gets merged, there's a want to add in functionality to separate out each pairs data into a separate sheet in a workbook for network-perf tests
### Description Let's try to make node-density-heavy great again. The main problem of this benchmark is that it can be "too heavy" depending on how the pods are scheduled. In...
### Description - Steps are documented here - https://docs.google.com/document/d/1KrQsFpHIuFg5Lv03muY__0-MlwftMFqgEsiroCkrBA0/edit#heading=h.24easisenadj - Tested on ROSA cluster ### Fixes
### Description The logic should be able now to detect if we're benchmarking a ROSA cluster. I also have added a custom profile for ROSA with higher etcd latencies thresholds...
1. After mb test, add another test_routes, to check if all the routes are still be able to work. If the last test_routes fails, the test should fail and not...
