GoKawiilRustConf Unconf yields draft guide for optimizing Tokio async apps
Following discussions at RustConf's Unconf event, developer Russell has begun drafting a living document of best practices for writing performant applications on Tokio's async runtime. The post outlines general principles, emphasizing that performance issues are highly context-dependent and that developers should first confirm a real problem exists before optimizing.
GoKawiil's interpretation of the reporting above, not reported fact.
Async Rust performance issues are notoriously hard to diagnose because they often only surface in production under specific workload conditions. A shared, community-vetted set of principles could help developers avoid chasing benign 'long poll' warnings and instead focus debugging efforts on actual application-level bottlenecks, saving significant engineering time.
- The document originated from a collaborative debugging and benchmarking discussion at RustConf's Unconf.
- Long poll times in Tokio apps are common but not always harmful, so developers should verify real metric impact before optimizing.
- Most performance issues stem from application code itself, particularly interactions between multiple tasks or components.
Source: dial9-rs.github.io, 2026-09-14
Published there as: “Principles for Fast Tokio Applications”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.