smol-rs / smol-rs/async-executor
"Next task" optimization
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 459
- Forks
- 52
- Avg merge
- 6h 53m
- Merged PRs (30d)
- 1
Description
In many actor systems (most notable Erlang), executors are optimized by having a "next task" slot in each executor queue. Whenever a new Runnable is scheduled, the future is first pushed to a slot separate from the normal queue. If a Runnable is already in this slot, it is pushed to the back of the queue. When it comes time to read from this queue, the slot is checked and popped from before the normal queue is.
This is optimal because if a task wakes another task to be immediately executed, the second task will be queued up immediately, which can emulate sequential computations very well.
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
The issue names no files or tests. Start by locating where Runnable values are scheduled and where executor queues are read, then trace how a task that wakes another task is ordered. Done means implementing and validating a per-executor next-task slot whose task is consumed before the normal queue, without losing queued work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100