News for hackers. Stuff that matters.
Re:Async Rust never left the MVP state by K0nserv on Tuesday May 05, 2026 @08:06AM (#48021337)
This is a great question and there isn't a definitive answer provided in the sources I linked.

Broadly I think there are three approaches:

1. For frequent and small CPU heavy tasks, just run them on the IO threads. As long as you don't leave too long between `.await` points (~10ms) it seems to work okay.

2. Run your sans-io code on a dedicated CPU thread and do IO from an async runtime. This introduces overhead that needs to be weighed against the amount of CPU work.

3. Have the sans-io code output something like `Output::DoHeavyCompute { .. }` and later feed the result back as `Input::HeavyComputeResult { .. }`, in the middle run the work on a thread pool.

Re:Async Rust never left the MVP state by K0nserv on Wednesday May 06, 2026 @04:51AM (#48033881)
Realised all of these examples are for async, but they apply equally for sync.