This module is also published under the name prokio on crates.io.
- Select I/O and timers that works with the target runtime.
- Native Runtimes usually require
Sendfutures and WebAssembly types are usually
To alleviate these issues, Yew implements a single-threaded runtime that executes
On platforms with multi-threading support, Yew spawns multiple independent runtimes
proportional to the CPU core number. When tasks are spawned with a runtime handle, it will
randomly select a worker thread from the internal pool. All tasks spawned with
will run on the same thread as the thread the task was running. When the runtime runs in a
WebAssembly target, all tasks will be scheduled on the main thread.
This runtime is designed in favour of IO-bounded workload with similar runtime cost. When running I/O workloads, it would produce a slightly better performance as tasks are never moved to another thread. However, If a worker thread is busy, other threads will not be able to steal tasks scheduled on the busy thread. When you have a CPU-bounded task where CPU time is significantly more expensive, it should be spawned with a dedicated thread (or Web Worker) and communicates with the application using channels.
Yew platform provides the following components:
- A Task Scheduler that is capable of running non-Send tasks.
- A Timer that is compatible with the scheduler backend.
- Task Synchronisation Mechanisms.
The Yew runtime is implemented with different runtimes depending on the target platform and can use all features (timers / IO / task synchronisation) from the selected native runtime: