EVP tests high volatility results
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 9
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
Some test produce quite volatile results on higher threads count (>= 8). Here is how these results look on charts:
The list of test and commands:
- evp_cipher -o evp_isolated -a AES-128-CBC -t 16
- evp_cipher -o evp_isolated -a AES-256-CBC -t 16
- evp_cipher -o evp_shared -a AES-128-CBC -t 16
- evp_cipher -o evp_shared -a AES-256-CBC -t 16
- evp_hash -o evp_isolated -a SHA1 -t 16
- evp_hash -o evp_isolated -a SHA256 -t 16
- evp_mac -o evp_isolated -t 16
- evp_mac -o evp_shared -t 16
- evp_mac -o deprecated_isolated -t 16
- evp_mac -o deprecated_shared -t 16
- providerdoall -t 16
- x509storeissuer -t 16
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.
Research direction
Start by running the listed evp_cipher, evp_hash, evp_mac, providerdoall, and x509storeissuer commands with 16 threads and compare the results with the reported charts. The issue does not name files or define a fix, so first identify where these EVP tests are implemented and agree on a reproducible criterion for reducing or explaining the volatility.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- performance, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100