Create performance tests
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- java
- Domain
- documentation, performance, testing
Research direction
Start by reading the README to understand the matching engine and where performance results should be documented. Identify the existing test and build entry points before adding performance tests, then run them and record the results in the README.
Written by the indexing model from the issue text.
Description
Add performance tests and share results in README.
- Dominant language
- Java
- Stars
- 23
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from Laffini/Java-Matching-Engine-Core
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 20/100
-
JSON schemas Opendocumentation enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
good first issue
Difficulty 3/5 1-2 days Newbie friendliness 35/100
All issues in Laffini/Java-Matching-Engine-Core
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
opensearch-project/k-NN#3597 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100