async-executor
async-executor copied to clipboard
smol-rs
Async executor
Two major changes significantly improve performance: - When `Executor::run()` is called, a handle to the local queue and ticker are cached into TLS. This lets tasks schedule to a thread-local...
Would it make sense for this crate to support `no_std + alloc`? I thought of smol when searching for a async executor in embedded rust.
Upon investigating https://github.com/bevyengine/bevy/issues/6941, we've found that thread wakeup times have been a significant bottleneck when spinning up large batches of tasks, like those mentioned in #91. Would it be possible...
Pre-1.9.0, you could spawn tasks on one thread, and then manually tick on another without issue since all tasks were queued into the global injector queue. Now that spawn prioritizes...
https://github.com/bevyengine/bevy/issues/12044 reports that the update to 1.9.0 is SemVer compatible with the prior 1.7.x and 1.8.x releases, and is currently causing all new fresh fetches and builds of Bevy to...
For some workloads many tasks are spawned at a time. This requires locking and unlocking the executor's inner lock every time you spawn a task. If you spawn many tasks...
This segment of code has assumptions that are incorrect for projects making use of multithreaded Wasm: https://github.com/smol-rs/async-executor/blob/6c70369102f947a9f4abc48c370c5ab8e7810840/src/lib.rs#L276-L288 Multithreaded Wasm is possible with Rust, but the chief limitation is that the...
Bevy's use of async_executor tends to be very bursty, with a single thread that adds tens or hundreds of tasks in short bursts. This might be running up against the...
It is my current opinion that `try_tick` is almost never useful for the purposes that I've seen people use it. The intended purpose is for FFI interop with other runtimes....