Tokio 1.0 – async runtime for Rust
1–10 of 422 posts
Re: Tokio 1.0 – async runtime for Rust
#2The changelog can be found here: https://github.com/tokio-rs/tokio/releases/tag/tokio-1.0.0
Re: Tokio 1.0 – async runtime for Rust
#3Congrats to the Tokio team! This is a big deal for the Rust ecosystem.
Re: Tokio 1.0 – async runtime for Rust
#4They mention working on using io_uring for filesystem calls for 2021. I wonder if there will be an option to use io_uring (instead of epoll) for networking calls as well? Handling network packets and events completely in userspace should allow for lower latency due to no more context switches to and from the Kernel, right?
Re: Tokio 1.0 – async runtime for Rust
#5As someone who has criticized Rust for the small standard lib and lack of stability in the ecosystem I'm very, very happy for this. This is one of the biggest milestones for Rust. Rust itself is great enough. The lack of a de facto async runtime and libs for your standard networking needs were a real barrier for non-enthusiasts environments. It will help its adoption in general purpose business apps, I guess and hope.
Re: Tokio 1.0 – async runtime for Rust
#6Congrats! I've fallen off Rust due to pivoting at work plus trying other languages but I'm intrigued again by Tokio's announcement. I'll be trying out your tutorial soon!
Re: Tokio 1.0 – async runtime for Rust
#7They mention working on using io_uring for filesystem calls for 2021. I wonder if there will be an option to use io_uring (instead of epoll) for networking calls as well? Handling network packets and events completely in userspace should allow for lower latency due to no more context switches to and from the Kernel, right?
We are definitely exploring this as well. There are a few possible ways to move forward on this. I'm not sure which is best yet, but with 1.0 out, we are going to be able to put more time into it.
Re: Tokio 1.0 – async runtime for Rust
#8Can someone explain to a non-rustacean what Tokio introduces that's not part of Rust? It looks like Rust provides the async/await semantics, so I'm guessing this is an event loop and dispatching system?
Re: Tokio 1.0 – async runtime for Rust
#9Can someone explain to a non-rustacean what Tokio introduces that's not part of Rust? It looks like Rust provides the async/await semantics, so I'm guessing this is an event loop and dispatching system?
Replying to myself, I found this bit in the docs explaining how Tokio decorates the main:
> An async fn is used as we want to enter an asynchronous context. However, asynchronous functions must be executed by a runtime. The runtime contains the asynchronous task scheduler, provides evented I/O, timers, etc.
Re: Tokio 1.0 – async runtime for Rust
#10Can someone explain to a non-rustacean what Tokio introduces that's not part of Rust? It looks like Rust provides the async/await semantics, so I'm guessing this is an event loop and dispatching system?
The Rust language provides the async/await syntax, which can turn imperative code into Future objects, but to run those Future objects, you must repeatedly call their poll method. Tokio is the piece of code that calls that method. It does so in a manner such that futures are only polled if able to continue work, and not e.g. waiting for a timer.
Besides that it provides lots of utilities for working with async code.