Automated benchmarks
- Dominant language
- Go
- Stars
- 610
- Forks
- 63
- Avg merge
- 12h 28m
- Merged PRs (30d)
- 57
Description
Terraform scripts to run on demand and a subset of connectors. Sets up a benchmark. Runs X number of records through the database to see if we
Not every permutation of connector and database but close ;-)
Benchmarks for the internals of conduit.
Types:
1. Integration Benchmark - Useful for end users.
2. Unit Benchmarks - These are useful for us.
Contributor guide
Research direction
Start by identifying the Terraform entry points, supported connectors, and database targets needed to run benchmarks on demand. Define how integration benchmarks for end users differ from unit benchmarks for Conduit internals, and document what record counts, connector/database coverage, and successful results should be measured.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, terraform
- Domain
- data-engineering, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100