Add some synthetic randomness to timing
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 70
- Forks
- 16
- Avg merge
- 4h 36m
- Merged PRs (30d)
- 30
Description
Various Janus components use repeated sleeps or intervals to schedule operations. We may want to add some randomness to the timing of these , both to smooth out the arrival time of requests we make to other aggregators, and to avoid nonlinear responses arising from timing loops going in and out of phase with each other.
This work depends on #445.
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 reading the dependency issue #445, then locate the Janus components that use repeated sleeps or intervals for scheduling. The issue does not name files, tests, or an acceptance criterion; completion would require agreeing on how timing randomness should smooth aggregator request arrivals and avoid synchronization effects.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100