rust-random / rust-random/book
Update RNG performance stats
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 59
- Forks
- 27
- Avg merge
- 3h 56m
- Merged PRs (30d)
- 1
Description
The rngs repository benchmarks have been updated to use Criterion and report cycles-per-byte (https://github.com/rust-random/rngs/pull/34); we likely use that, either duplicating the framework to the rand repository or by adding dev-dependencies in rngs to all the RNGs we want to benchmark.
We should wait until the next rand release, at least to get all RNGs on the same version of rand_core.
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 updated benchmarks in rngs pull request 34 and the current benchmark setup in the rand repository. Confirm that the next rand release has aligned rand_core versions, then determine whether to duplicate Criterion or add rngs dev-dependencies. Done means the RNG benchmarks report cycles-per-byte using the selected approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100