RoaringBitmap / RoaringBitmap/roaring-rs
Migrate to cargo criterion
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 957
- Forks
- 119
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 1
Description
https://github.com/bheisler/cargo-criterion
- cargo-criterion seeks to improve iteration time for Criterion-rs benchmarks. By moving functionality into a separate executable which can be installed once and reused, Criterion-rs can shrink - meaning less code to compile and link into the benchmarks themselves.
- Because cargo-criterion can oversee the whole benchmark process from beginning to end, it's better placed to deliver features that would be difficult to implement in Criterion-rs. These include:
- Machine-readable output
- Tracking benchmarked performance over time
This is fantastic. Want. In addition to the above we can get rid of html-reports feature of criterion and bench will have much few dependencies -> faster CI builds.
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 reviewing the repository's Criterion-rs benchmark configuration and the cargo-criterion project linked in the issue. Migrate the benchmark process to cargo-criterion, remove the criterion html-reports feature where applicable, and verify that CI builds still complete with fewer benchmark dependencies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100