Performance tests: remaining tasks

[elsand]

Tasks

Preview Give feedback

1. Establish stable and performant test runners for GitHub test workflows
2. Establish performance threshold values
3. Define tests and establish workflows for tests
4. Populate YT01 with data #1574
   +0
   
5. Enable autogrowth of storage in PostgreSQL
6. Enable sufficient performance tier (max IOPS)
7. Click-ops max_connections to reset to SKU default for all environments

Establish stable and performant test runners for GitHub test workflows

In order to yield reproducible and realistic results, we need to have separate runners for the GitHub test workflows to execute, as the free ones supplied by GitHub offer low and very variable performance. Coordinate with team platform.

Establish performance thresholds

We want to be able to track performance regressions, so we need to establish threshold values (eg. P95 RPS values) for the various tests, which will fail the tests if below that threshold.

Define tests and establish workflows for tests

When thresholds are found, we need to create workflows that 1) run one or several performance tests with a particular configuration (duration, VUs etc) 2) parse the results 3) compare the results with defined threshold values and mark the test as either passed or failed

Populate YT01 with data

In order to have a realistic foundation on which the SUT to run, we need to populate the database with a non-trivial amount of data. For now, this is a one-time job.

Enable auto_growth of storage in PostgreSQL

Should be defined in IAC, and if needed clickopsed for existing PostgreSQL instances

Enable sufficient performance tier (max IOPS)

Should be defined in IAC, and if needed clickopsed for existing PostgreSQL instances

Click-ops max_connections to reset to SKU default for all environments

Should be defined in IAC, and if needed clickopsed for existing PostgreSQL instances