-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
3
-
False
-
None
-
False
-
AppSvc Sprint 217
Story (Required)
A set of KPI (Key Performance Indicators) should be computed out of the data collected during the SBO performance test that can be used to compare one test run with another (for instance, one run with master and second run with PR to show the effect the PR has on performance/usage)
Background (Required)
Currently, the data collected during the SBO performance test (https://gitlab.cee.redhat.com/ocpappsvc/ocpappsvc-qe/-/tree/main/sbo-on-sb-perf) is a set of timestamped CSV files for various Kubernetes resources, incl. SBO pod, in terms of CPU and Memory usage from the whole duration of the test.
Additionally, SBO performance metrics such as TimeToReconcile (time between SB resource creation and when it was picked up by SBO) or ReconciledToDone (time between when SB resource was picked up by SBO and when the binding is done).
Approach(Required)
For the selected set of metrics a statistic analysis of the values over the whole duration of the test would be computed with the following statistic data values:
- first value
- last value
- minimum
- maximum
- average
- median
The selected metrics would be:
- CPU and Memory usage of SBO pod
- TimeToReconcile, ReconcileToDone and TimeToDone metrics for all the scenarios included in the performance test
The KPIs will be stored in a form of YAML file so that it can be human and machine readable.
Acceptance Criteria
Set of KPI is computed out of the data collected as results of the SBO on SB performance test
The statistic summary of all the KPIs is stored in kpi.yaml file and archived in the performance testing job
- is related to
-
APPSVC-1105 Evaluate performance of SBO in upstream PRs on-demand
- Closed