-
Notifications
You must be signed in to change notification settings - Fork 930
The Performance Testing Setup
Nok Lam Chan edited this page Oct 29, 2024
·
4 revisions
The performance tests are splitted into two parts:
- Component Benchmark
- Pipeline Test
The tests are now triggered as a Github Action job:
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
[WIP]
- Contribute to Kedro
- Guidelines for contributing developers
- Contribute changes to Kedro that are tested on Databricks
- Backwards compatibility and breaking changes
- Contribute to the Kedro documentation
- Kedro documentation style guide
- Creating developer documentation
- Kedro new project creation - how it works
- The CI Setup: GitHub Actions
- The Performance Test Setup: Airspeed Velocity
- Kedro Framework team norms & ways of working ⭐️
- Kedro Framework Pull Request and Review team norms ✍️
- Insights and opportunities related to helping Kedro impact more users
- Research summary of insights for improving Kedro's value
- Synthesis of research related to deployment of Kedro to modern MLOps platforms
- Market research on versioning tools
- Versioning research
- Research summary of insights for redesigning Kedro's data catalog API
- Research on Deployment