A global, auto-scaling scheduler for [async-task] using work-balancing.
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2025-05-12 13:16:01 -04:00
benches fix 2024-06-20 17:30:51 -05:00
examples greatly improve performance and fairness: 2022-06-27 14:40:21 -05:00
src Remove SMOLSCALE_PROFILE and change log level to trace 2025-05-12 13:15:51 -04:00
.gitignore hf 2021-06-23 18:05:13 -05:00
Cargo.toml chore: Release smolscale version 0.4.16 2025-05-12 13:16:01 -04:00
README.md fix 2022-11-04 12:28:48 -05:00

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