Details
-
Task
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
This is an epic-like issue - I propose creating smaller and close issues from this.
For the moment our main target is to provide performance measurements for the MariaDB server issues, https://jira.mariadb.org/browse/MCOL-5853 . So far we have to do this by hands, but we need to automate the whole process.
I think the subtask list looks like:
1. configure the MariaDB releases of interest, e.g. 11.4 or 10.6. The framework must automatically fetch the last tags by minor versions (e.g. 11.4.4) and start procedure for it (deploy and build the server, run burza)
2. Configure comparisons of interest (e.g. compare 11.4 with 10.6): keep the data between the runs of the batch task and make an aggregate report. E.g. we still should remove the very old data, maybe Prometheus can evict them like for last 30 days - in this case we don't need to do anything. Maybe this task can be solely solved with Prometheus/Grafana
The target for this task is to do measurements, like MCOL-5853, and get results fully automatically, maybe with only configuring which releases to test
Attachments
1.
|
Benchmark data processing |
|
Closed | Konstantin Kovalev (Inactive) |
2.
|
Reports rendering |
|
Open | Unassigned |
3.
|
Results processing |
|
Open | Unassigned |