smol-rs / smol-rs/async-executor
Consider using st3 for work-stealing
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 459
- Forks
- 52
- Avg merge
- 6h 53m
- Merged PRs (30d)
- 1
Description
st3 looks to be a fairly promising public crate for implementing tokio's !Send local worker queues which eliminate most of the atomic operations when popping from the local queue.
Right now async_executor uses concurrent_queue for these purposes, but realistically only the workstealing operations need to be threadsafe, the local worker popping from the queue does not actually need to be Send.
Some additional scrutiny on it's thread safety model and some API compatibility additions are definitely needed (see asynchronics/st3#2).
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 how async_executor currently uses concurrent_queue for work-stealing and read the referenced st3#2 discussion. Validate st3's thread-safety model and required API compatibility before deciding whether it can replace the current queue implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100