marigold-dev / marigold-dev/deku
Smarter block time delays
Nobody has claimed this yet.
- Dominant language
- OCaml
- Stars
- 82
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
We currently delay blocks by 1 second. The only purpose this delay is to prevent flooding the terminal during manual tests. However, this slows the chain down artificially when doing our benchmarks (in #539).
I made this delay configurable in #682.
@EduardoRFS has suggested we do the following instead:
- if there are any pending operations that we can apply, don't delay at all - immediately distribute the next block.
- if there are no pending operations we can apply, wait a configurable amount of time (he suggests 5s default).
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 the current one-second block delay and the configurable delay introduced in #682. Trace how pending operations are detected and blocks are distributed, then compare the behavior against the benchmark context in #539: pending operations should proceed immediately, while an empty queue should use the configured wait.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- blockchain, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100