Add benchmark tests
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 149
- Forks
- 59
- PR merge metrics
- No merged PRs in 30d
Description
Having benchmarks will make finding bottlenecks in the code easier. Since this is a low level library having basic benchmarks make sense. This library may be deprecated soon but with its current use is worth benchmarking for easy optimizations.
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
The issue names no files, tests, or entry points. Start by inspecting the repository for the low-level code and existing test conventions, then identify representative paths to benchmark. Done means benchmark tests exist for the relevant library behavior and can be run to compare performance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- performance, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100