4 ms·
Rust Async WG member here: This question comes up pretty regularly when people first learn about async Rust. I suspect it’s because performance is often emphasi
by yoshuaw 4y ago
Rust Async WG member here: This question comes up pretty regularly when people first learn about async Rust. I suspect it’s because performance is often emphasized as the main benefit of async Rust.
In my opinion performance is always relative and dependent on the workload. Instead it’s worth looking more at which capabilities async Rust provides which aren’t present in non-async Rust. This includes ad-hoc cancellation, ad-hoc concurrency, and combining the two into things such as timeouts.
I wrote a post explaining this in detail a few months ago: https://blog.yoshuawuyts.com/why-async-rust/ https://blog.yoshuawuyts.com/why-async-rust/
- vlovich123 4y agoDoes async have an impact on tail latency? I feel like async + iouring should provide substantially better consistency for latency (+ lower) but I haven’t seen any measurements confirming this yet.
- pkolaczk 4y agoFor me it's also ability to run multiple concurrent actions on shared state without need for synchronization, Arc or dealing with Rust lifetimes. A simple loop with select! is hard to overrate.