diesel_async
tokio-uring
Our great sponsors
diesel_async | tokio-uring | |
---|---|---|
9 | 28 | |
535 | 981 | |
- | 1.7% | |
7.0 | 4.1 | |
13 days ago | 26 days ago | |
Rust | Rust | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
diesel_async
-
Diesel 2.0.0 RC1
The already linked discussion from last time already contains a lot of information about this. Diesel itself does not provide async operations and that will likely remain that way for a foreseeable future. At least my preferred solution is to keep async support in a separate crate. A prototype for this is currently available here. Keep in mind that this is not released yet, so there might be bugs everywhere. I plan to cut a first release of this crate after the final release of diesel 2.0, which means hopefully soon. As for ETA's: I generally do not give any ETA's for releases, as this is currently a free time project for me.
-
Any active open source repos built using Rust that need development ?
So, diesel is an ORM that tries to take full advantage of rust's typing expressivity to allow for statically checked, and fast, queries. I absolutely loved it when trying it out the first time.
-
Reviews of the Diesel ORM, are there better alternatives?
i don't see why you or anyone else would consider it too big of an issue that Diesel doesn't have async. For those who really want async diesel right now, the author already released diesel_async as a stop-gap solution, but even without that there's nothing wrong with using spawn_blocking. It feels worse than it really is to use blocking thread pools; until io_uring is a thing, there's no real getting around the necessity of threads being blocked for I/O and so adding async to the mix doesn't magically make things faster.
-
What is your go-to database crate for PostgreSQL?
As for now there is an prototype available here. It's technically feature complete, but depends on a unpublished diesel version + has some remaining bugs with certain mysql versions. If that is fixed I will likely publish a first alpha version officially. That can take same time because that's a second large project that needs maintenance time beside diesel itself and that's quite a lot to do in my free time. You can support this work by sponsoring me on github
-
Diesel 2.0.0 RC.0
Async support for diesel currently lives in a separate repository as there are language level blocking issues for publishing a version of this crate where we could commit to a stable release at all. See the corresponding diesel issue for details.
-
Async Rust in 2022
https://github.com/weiznich/diesel_async tho'.
-
diesel-async: An async version of diesel
Weiznich (the maintainer of Diesel) has created an experimental async version of the diesel Connection and RunQueryDsl traits, which should help with ease-of-use for Diesel within async contexts. It is not yet published on crates, but you can find it here: https://github.com/weiznich/diesel_async
- In Defense of Async: Function Colors Are Rusty
tokio-uring
- tokio_fs crate
-
Use io_uring for network I/O
While Mio will probably not implement uring in its current design, there's https://github.com/tokio-rs/tokio-uring if you want to use io_uring in Rust.
It's still in development, but the Tokio team seems intent on getting good io_uring support at least!
As the README states, the Rust implementation requires a kernel newer than the one that shipped with Ubuntu 20.04 so I think it'll be a while before we'll see significant development among major libraries.
-
Create a data structure for low latency memory management
That's what the pool is for: https://github.com/tokio-rs/tokio-uring/blob/master/src/buf/fixed/pool.rs
To add on this, we're adding infrastructure for fixed buffers pre-registered with the kernel into tokio-uring.
-
Cloudflare Ditches Nginx for In-House, Rust-Written Pingora
I think io_uring support [0] still is not production ready.
Tokio supports io_uring (https://github.com/tokio-rs/tokio-uring), so perhaps when it's mature and battle-tested, it'd be easier to transition to it if Cloudflare aren't using it already.
-
Anyone using io_uring?
- Tokio suffers from a similar problem
-
redb 0.4.0: 2x faster commits with 1PC+C instead of 2PC
Eg via tokio-uring.
-
Efficient way to read multiple files in parallel
I strongly recommend you to look into io-uring and use async executors that take advantages of it: - tokio-uring (not recommended as it is still undergoing development) - monoio - glommio
-
How to use async Rust for non-IO tasks?
There's a new API on Linux called io_uring that has performance benefits, but most executors don't use it yet, except executors meant specifically to harness the power of io_uring like tokio-uring and Glommio
What are some alternatives?
libuv - Cross-platform asynchronous I/O
glommio - Glommio is a thread-per-core crate that makes writing highly parallel asynchronous applications in a thread-per-core architecture easier for rustaceans.
liburing
monoio - Rust async runtime based on io-uring.
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
rbatis - Rust Compile Time ORM robustness,async, pure Rust Dynamic SQL
bb8 - Full-featured async (tokio-based) postgres connection pool (like r2d2)
mirrord - Connect your local process and your cloud environment, and run local code in cloud conditions.
rust-analyzer - A Rust compiler front-end for IDEs [Moved to: https://github.com/rust-lang/rust-analyzer]
diesel - A safe, extensible ORM and Query Builder for Rust
prisma-client-rust - Type-safe database access for Rust
rust.vim - Vim configuration for Rust.