LIghtning Talk: 'tokio' and 'atspi'
summary
Claims that async runtimes including Tokio and other async executors fail to prevent stale data and ordering races when talking to AT-SPI over D‑Bus (using the c‑bus crate). Measured P99 latency on a Raspberry Pi is over 10 seconds. A new screen reader (Odelia) hits these limits because every node read forces a full IPC round trip, so a redesigned assistive‑technology API and different synchronization primitives are being built.
AI-written summary · about
related talks
05m“Using async-profiler to Find Tail Latency Issues”
32mTechniques for writing concurrent applications with asynchronous I/O
29mI/O in Rust: the whole story
29mAsychronous programming in Rust
46mA Tale of Two Asyncs
45mKeynote | Actors with Tokio – a lesson in ownership
36masync/await with async-std
23mEmbrace or ditch the async?