open-telemetry / open-telemetry/opentelemetry-python
Ensure benchmark tests cover all common operations defined in spec
Open
Nobody has claimed this yet.
triaged
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 19
Description
Followup to discussion in #335, this issue is to ensure all the operations defined in the performance benchmarking specification are covered by our existing benchmarks:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the performance benchmarking specification linked in the issue and then inspect the repository's existing benchmark tests. Compare the defined operations with current coverage; done means every common operation in the specification is represented by an existing benchmark.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100