Concurrency
Graceful Shutdown in Tokio With Signals and Task Tracking
Shut down a Tokio service cleanly: catch SIGTERM and Ctrl+C, stop accepting work, wait for in flight tasks with TaskTracker, then exit within a deadline.
7 min read
Tag
tokio
33 posts
Concurrency
Cancelling Tasks in Tokio With Abort and Cancellation Tokens
Stop a Tokio task three ways: JoinHandle::abort, a CancellationToken for cooperative shutdown, and dropping a future. See what each does to cleanup.
7 min read
Concurrency
Tokio Select and Cancellation Safety Explained With Traps
select! races futures and drops the losers, which is only safe if they can be dropped mid way. Learn what cancellation safe means and which APIs are not.
7 min read
Concurrency
Spawn Blocking in Tokio and When Rayon Is the Better Tool
Both move blocking work off the async threads, but they differ in pool, limits and fit. See which to pick for file I/O, hashing and number crunching.
7 min read
Concurrency
JoinSet in Tokio for Managing Many Tasks as a Group
JoinSet owns a group of spawned tasks and returns their results as they finish. See spawn, join_next, abort_all and how errors and panics surface.
8 min read
Concurrency
Why Tokio Spawn Needs a Static Future and How to Cope
tokio::spawn demands a future that owns its data. Learn why the compiler asks for static, what it does and does not mean, and four ways to share data with a task.
7 min read
Concurrency
Spawning Tasks With tokio spawn and Joining Their Results
Spawn tasks with tokio::spawn, wait for them with JoinHandle and collect results with JoinSet. Includes the Send and static bounds and the panics join returns.
8 min read
Concurrency
Tokio Runtime Explained Workers Tasks and the Scheduler
What the Tokio runtime is made of: worker threads, a task queue, an I/O driver and a timer. See how multi-thread and current-thread flavors differ.
7 min read
Editor's pick
ConcurrencyGuide
Async Rust and Tokio From Futures to a Production Service
A guide to async Rust and Tokio: futures, the runtime, spawning, blocking, channels and the mistakes that make a service stop answering.
16 min read