16 releases

0.6.0 Dec 22, 2024
0.5.12 Nov 23, 2024
0.5.11 Oct 15, 2024
0.5.8 Aug 6, 2024
0.4.9 Feb 7, 2024

#377 in Concurrency

Download history 435/week @ 2024-12-18 161/week @ 2024-12-25 102/week @ 2025-01-01 107/week @ 2025-01-08 67/week @ 2025-01-15 133/week @ 2025-01-22 106/week @ 2025-01-29 295/week @ 2025-02-05 151/week @ 2025-02-12 315/week @ 2025-02-19 107/week @ 2025-02-26 262/week @ 2025-03-05 45/week @ 2025-03-12 47/week @ 2025-03-19 154/week @ 2025-03-26 134/week @ 2025-04-02

534 downloads per month
Used in 5 crates

ISC license

48KB
1K SLoC

smolscale

A global, auto-scaling scheduler for [async-task] using work-balancing.

What? Another executor?

smolscale is a work-balancing executor based on [async-task], designed to be a drop-in replacement to smol and async-global-executor. It is designed based on the idea that work-stealing, the usual approach in async executors like async-executor and tokio, is not the right algorithm for scheduling huge amounts of tiny, interdependent work units, which are what message-passing futures end up being. Instead, smolscale uses work-balancing, an approach also found in Erlang, where a global "balancer" thread periodically balances work between workers, but workers do not attempt to steal tasks from each other. This avoids the extremely frequent stealing attempts that work-stealing schedulers generate when applied to async tasks.

smolscale's approach especially excels in two circumstances:

  • When the CPU cores are not fully loaded: Traditional work stealing optimizes for the case where most workers have work to do, which is only the case in fully-loaded scenarios. When workers often wake up and go back to sleep, however, a lot of CPU time is wasted stealing work. smolscale will instead drastically reduce CPU usage in these circumstances --- a async-executor app that takes 80% of CPU time may now take only 20%. Although this does not improve fully-loaded throughput, it significantly reduces power consumption and does increase throughput in circumstances where multiple thread pools compete for CPU time.
  • When a lot of message-passing is happening: Message-passing workloads often involve tasks quickly waking up and going back to sleep. In a work-stealing scheduler, this again floods the scheduler with stealing requests. smolscale can significantly improve throughput, especially compared to executors like async-executor that do not special-case message passing.

License: ISC

Dependencies

~11–44MB
~634K SLoC