nebari
tokio-uring
nebari | tokio-uring | |
---|---|---|
11 | 28 | |
260 | 1,010 | |
2.3% | 2.8% | |
4.6 | 4.1 | |
8 months ago | 3 months 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.
nebari
-
Some key-value storage engines in Rust
Or, you could also look at Nebari, which underlies BonsaiDB https://github.com/khonsulabs/nebari/
-
Are there a demand for management system of embedded storage like RocksDB? I plan to build one in Rust as the language becoming a core of many popular databases but wonder if there’s a demand. Can’t find any similar project even in other languages.
There is Nebari which is the KV part of BonsaiDB I've used both successfully (and that is currently in production)
-
redb 0.4.0: 2x faster commits with 1PC+C instead of 2PC
This looks like it could have been inspired by BonsaiDB's recent problems. I think the authors are now trying to achieve something similar to your project with a new storage layer called Sediment (which will become a part of Nebari if successful).
-
File read performance comparison
I ran my benchmark suite on my 2017 i7 MacBook Pro (Filevault enabled), and I was able to perform a random "get" operation out of a 1 million record dataset in an average of 18us (microseconds).
-
Announcing BonsaiDb v0.2.0: Custom Primary Keys, LZ4 Compression
I haven't spent much time documenting the low-level structures outside of the code itself.
-
Announcing BonsaiDb v0.1.0: A Rust NoSQL database that grows with you
Nebari, the underlying storage layer, also has its own coverage report.
-
Benchmarking relational data in BonsaiDb, a Rust-native NoSQL database
Quite well, but Sled doesn't support the same feature set. I've benchmarked our low-level storage layer against Sled in its own repostiory: Nebari Benchmark README. There are two links two criterion reports on that page.
-
Are there any big projects written in Rust without any use of unsafe code?
I maintain several large codebases that have #![forbid(unsafe)] annotations, which prevent unsafe code from being written in those codebases directly. BonsaiDb clocks in at just shy of 30k LOC, and depends on Nebari which is another 12k LOC. Those two crates make up the bulk of a networked database implementation.
-
What is the best key-value store for Rust 2021
I have, and there's a set of microbenchmarks in the repository. There are two links to reports on that page -- one that's executed on GitHub Actions, which can have quite widely varying performance, and one that's executed on a "dedicated" VPS instance from Scaleway -- exact specs are on that page. I've kicked off another run on that VPS, since it hasn't been run since October. It takes a while to run, so if it still says October, try hitting refresh a little later.
-
What's everyone working on this week (40/2021)?
I replaced Sled in BonsaiDb with a new storage layer I wrote: Nebari. I just wrote a post this morning recalling my struggles over the last month to feel comfortable sharing this project outside of a smaller group of people.
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
-
Cloudflare Ditches Nginx for In-House, Rust-Written Pingora
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
-
Stacked Futures and why they are impossible
This is my thinking as well. Specifically, I realized that if you don’t use tasks, but rather futures and join, than structured concurrency just works out (at the cost of less efficient poll). In a single-threaded/thread-per-core runtime, tasks could have the same semantics as futures. Somewhat elaborated here: https://github.com/tokio-rs/tokio-uring/issues/81
-
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
-
Side effects of Tokio
Breaking it down a bit further- Rust's async is zero-cost, and there's no way to write faster equivalent code to the language construct in Rust (and presumably other LLVM languages). Tokio introduces abstractions over OS APIs (indirectly) and provides a runtime. The runtime isn't zero cost, but it is likely to be better optimized for "standard" situations than a homebrewed solution, and its primary competition is in the form of other large async runtimes. On the other hand, Tokio's IO routines are (AFAIK) about as well written as one can get with blocking OS APIs, and the only competitors in that space are projects like tokio-uring that use APIs more well suited for asynchronous usage.
What are some alternatives?
glow - GL on Whatever: a set of bindings to run GL anywhere and avoid target-specific code
libuv - Cross-platform asynchronous I/O
forbidden - An auth system/library for Rust applications
glommio - Glommio is a thread-per-core crate that makes writing highly parallel asynchronous applications in a thread-per-core architecture easier for rustaceans.
sled - the champagne of beta embedded databases
liburing
redb - An embedded key-value database in pure Rust
monoio - Rust async runtime based on io-uring.
PickleDB - PickleDB-rs is a lightweight and simple key-value store. It is a Rust version for Python's PickleDB
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
bonsaidb - A developer-friendly document database that grows with you, written in Rust
diesel_async - Diesel async connection implementation