The Performance Testing Setup
The performance tests are split into two parts:
- Component Benchmark
- Pipeline Test
The tests are now triggered as a Github Action job:
We use asv for our component benchmark. Check the guide for running this locally.
The benchmark result is updated when new commit arrives main, it triggers the Github Action and the result is tracked in kedro-benchmark-results
The benchmark can also be run locally using asv, the source code lives with the kedro repository
To run a pipeline performance test, open a pull request with the changes done to the Kedro repo and add the performance label to this pull request.
This will trigger a performance test comparing the elapsed time to run a pipeline using your current branch against the latest Kedro release. The results can be seen on the Github Actions details of your pull request.
