cachegrand
tokio-uring
Our great sponsors
cachegrand | tokio-uring | |
---|---|---|
24 | 28 | |
963 | 998 | |
- | 2.8% | |
8.0 | 4.1 | |
6 months ago | about 2 months ago | |
C | Rust | |
BSD 3-clause "New" or "Revised" License | 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.
cachegrand
-
C++ caching library with tiering (RAM + disc)
Closest that comes to my mind is CacheGrand. It doesn’t have some of the features yet, but I believe @daniele_dll is working on it!
-
[PC][Switzerland] Cheap Rackspace
I use this HW for benchmarking and testing my open source project cachegrand ( https://github.com/danielealbano/cachegrand)
- cachegrand
-
Cachegrand, a fast, Redis compatible, KV store – hashtable documentation
https://github.com/danielealbano/cachegrand/blob/main/docs/a...
When tested with memtier_benchmark, using the Redis protocol, cachegrand itself, on the benchmarking hardware, thanks to the implemented hashtable can reach up to 5 million GET op/s and up to 4.5 million UPSERT op/s without batching, with it up to 60 million GET op/s and up to 26 million UPSERT op/s!
- cachegrand - a blazing fast, Redis compatible, Key-Value store builf for today's hardware - hashtable documentation - capable of delivering up to 112 GET mop/s and 85 UPSERT mop/s on a EPYC 7502P
- Show HN: Cachegrand – a fast OSS Key-Value store built for modern hardware
- Cachegrand – a modern OSS Key-Value store built for today's hardware
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?
dragonfly - A modern replacement for Redis and Memcached
libuv - Cross-platform asynchronous I/O
varnish-cache - Varnish Cache source code repository
glommio - Glommio is a thread-per-core crate that makes writing highly parallel asynchronous applications in a thread-per-core architecture easier for rustaceans.
examples - Example data structures and algorithms
liburing
midi-redis - A toy memory store with great performance
monoio - Rust async runtime based on io-uring.
async-std - Async version of the Rust standard library
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
webdis - A Redis HTTP interface with JSON output
diesel_async - Diesel async connection implementation