Finalised report of the performance test

This commit is contained in:
pb
2025-05-28 12:26:29 +02:00
parent a9b5f6dcad
commit 3da3ada710
8 changed files with 67 additions and 7 deletions

View File

@@ -106,19 +106,19 @@ In order to monitor the ressource consumption during our tests we need to create
We create 4 different queries using Prometheus as the data source. For each query we can use the `code` mode to create them from a PromQL query.
## OC stack consumption
### OC stack consumption
```
sum(container_memory_usage_bytes{name=~"oc-auth|oc-datacenter|oc-scheduler|oc-front|oc-schedulerd|oc-workflow|oc-catalog|oc-peer|oc-workspace|loki|mongo|traefik|nats"})
```
## Monitord consumption
### Monitord consumption
```
sum(container_memory_usage_bytes{image="oc-monitord"})
```
## Total RAM consumption
### Total RAM consumption
```
sum(
@@ -128,8 +128,24 @@ sum(
)
```
## Number of monitord containers
### Number of monitord containers
```
count(container_memory_usage_bytes{image="oc-monitord"} > 0)
```
```
# Launch executions
We will use a script to insert in the DB the executions that will create the monitord containers.
We need to retrieve two informations to execute the scripted insertion :
- The **workflow id** for the workflow we want to instantiate, this is can be located in the DB
- A **token** to authentify against the API, connect to oc-front and retrieve the token in your browser network analyzer tool.
Add these to the `insert_exex.sh` script.
The script takes two arguments :
- **$1** : the number of executions, which are created by chunks of 10 using a CRON expression to create 10 execution**S** for each execution/namespace
- **$2** : the number of minutes between now and the execution time for the executions.