open-telemetry / open-telemetry/opentelemetry-java
Improve Benchmark consistency and visibility
Open
Nobody has claimed this yet.
Feature Request
- Dominant language
- Java
- Stars
- 2.5k
- Forks
- 1k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 58
Description
I've been involved in a cross-language initiative to improve our community's performance evaluation. Here are the things that I'm working on relating to this repo:
- add an org level shared runner that uses bare-metal to improve test consistency
- add a workflow to run JMH benchmarks via github actions
- request access to shared runner for added workflow on
main - publish results to a github pages branch
- publish results to otel website
- define cross language benchmark scenarios in spec
- implement/update benchmark in java repo to match spec
- ensure benchmark execution is constrained and short to prevent shared resource abuse
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 reviewing the unchecked items in the issue and the linked cross-language initiative and specification pull request. The completed workflow and benchmark work are linked from the checklist; completion would require resolving the remaining website publication, scenario definition, and Java benchmark alignment work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- performance, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100