RoaringBitmap / RoaringBitmap/roaring
Need for more profiling...
Open
Nobody has claimed this yet.
help wanted
performance
- Dominant language
- Go
- Stars
- 2.9k
- Forks
- 262
- Avg merge
- 2h 34m
- Merged PRs (30d)
- 8
Description
Though the code is well tested and works, and there has been several contributions to make it run faster, there could still be large inefficiencies. We should profile this code.
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 with the Go profiling guide linked in the issue, then determine which part of this repository should be profiled; no files, benchmarks, or entry points are named. Done is not defined beyond investigating possible inefficiencies, so the profiling target and success criteria need maintainer clarification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100