oasisprotocol / oasisprotocol/oasis-core
Runtime transaction scheduler lookahead
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
Currently the runtime transaction scheduler builds a batch by traversing the pending transactions (by priority) and stopping before the next pending transaction would cause any of the batch-weight limits to be reached.
A "big" transaction can cause the scheduler to not fully fill up the batch if there exist "smaller" transactions that could still be included in the batch.
Lookahead would somewhat mitigate this issue, but this would mean that sometimes a lower priority transaction could be scheduled before a higher priority "bigger" transaction (which is probably fine).
Originally posted by @kostko in https://github.com/oasisprotocol/oasis-core/pull/3965#discussion_r639553413
Contributor guide
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 runtime transaction scheduler and the logic that traverses pending transactions and enforces batch-weight limits. Read the discussion in PR 3965, then define tests showing that smaller lower-priority transactions can fill remaining capacity without violating batch limits; done means lookahead behavior is covered and the scheduler produces fuller batches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100