RoaringBitmap / RoaringBitmap/CRoaring
Should we standardize the output of our benchmarks?
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.9k
- Forks
- 334
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 17
Description
I've been toying with the idea of making CRoaring benchmarks print their results in a format compatible with the benchstat tool we use in the Go world for comparing different runs. I think it would help us make more informed decisions when optimizing.
Related to this, after we tackle #284 we should be able to use an allocator that keeps track of how many allocations we make and how much memory we use for a given operation, which could further aid comparison.
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 locating how CRoaring benchmarks currently print their results and compare that output with the format expected by Go's benchstat tool. Review the dependency on issue #284, then define the benchmark output and allocation and memory measurements that would make comparisons useful.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, go
- Domain
- performance, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100