79 releases

0.4.16 May 12, 2025
0.4.15 Feb 25, 2025
0.4.11 Aug 29, 2024
0.4.7 Jun 21, 2024
0.1.0 Oct 26, 2020

#1606 in Asynchronous

Download history 284/week @ 2025-10-08 355/week @ 2025-10-15 417/week @ 2025-10-22 210/week @ 2025-10-29 216/week @ 2025-11-05 229/week @ 2025-11-12 235/week @ 2025-11-19 211/week @ 2025-11-26 205/week @ 2025-12-03 199/week @ 2025-12-10 259/week @ 2025-12-17 229/week @ 2025-12-24 180/week @ 2025-12-31 123/week @ 2026-01-07 204/week @ 2026-01-14 166/week @ 2026-01-21

699 downloads per month
Used in 42 crates (33 directly)

ISC license

23KB
357 lines

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

~12–45MB
~644K SLoC