runtimelab
monoio
runtimelab | monoio | |
---|---|---|
2 | 23 | |
1 | 3,697 | |
- | 3.1% | |
0.0 | 7.7 | |
5 months ago | 21 days ago | |
Rust | ||
MIT License | Apache License 2.0 |
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.
runtimelab
- C# Green Threads Technical Report
-
The State of Async Rust
Yes it does. Those best practices are very easy to follow and are enforced by analyzers. I have never encountered those issues on a recent big project I worked on, although they were common in the past when async was new. Also the green threads research concluded that it's not worth adding it to NET:
https://github.com/davidwrighton/runtimelab/blob/report/docs...
monoio
- How to Visualize and Analyze Data in Open Source Communities
-
Core to Core Latency Data on Large Systems
There is also another thread-per-core implementation by ByteDance (TikTok) for Rust called Monoio with benchmarks[0] comparing it to Tokio and Glommio.
[0] https://github.com/bytedance/monoio/blob/master/docs/en/benc...
-
The State of Async Rust
My understanding is you always need a runtime, somethings needs to drive the async flow. But there are others on the market, just not without the.. market domination... of tokio.
https://github.com/smol-rs/smol looks promising simply for being minimal
https://github.com/bytedance/monoio looks potentially easier to work with than tokio
https://github.com/DataDog/glommio is built around linux io_uring and seems somewhat promising for performance reasons.
I haven't played with any of these yet, because Tokio is unfortunately the path of least resistance. And a bit viral in how it's infected tings.
-
Why does Actix-web's handler not require Send?
I assume Tokio itself, see e.g monoio or glommio, but also Seastar for C++.
-
Introducing `rudis`: A Sharded, Concurrent Mini Redis with Web Interface in Rust
I think monoio is also thread-per-core but also iouring https://github.com/bytedance/monoio. I don't know how you would shard certain keys into different threads, but if you can do that deterministically then there could be a significant speed up.
-
How does async Rust work
I believe this is also "thread-per-core".
-
Oxy is Cloudflare's Rust-based next generation proxy framework
Bytedance has their in-house monoio <https://github.com/bytedance/monoio> (supports io-uring) but it requires rust nightly.
-
Is async runtime (Tokio) overhead significant for a "real-time" video stream server?
There's another thread-per-core runtime called https://github.com/bytedance/monoio
-
Blessed.rs – An unofficial guide to the Rust ecosystem
It's worth mentioning: Under "Async Executors", for "io_uring" there is only "Glommio"
I recently found out that ByteDance has a competitor library which supposedly has better performance:
https://github.com/bytedance/monoio
https://github.com/DataDog/glommio/issues/554
-
hyper v1.0.0 Release Candidate 1
I see that, I also tried with monoio, but the developer of that runtime mentioned that https://github.com/bytedance/monoio/blob/master/examples/hyper_server.rs might have soundness issues
What are some alternatives?
website - Website for the Tokio project
glommio - Glommio is a thread-per-core crate that makes writing highly parallel asynchronous applications in a thread-per-core architecture easier for rustaceans.
rust - Empowering everyone to build reliable and efficient software.
tokio-uring - An io_uring backed runtime for Rust
AspNetCoreDiagnosticScenarios - This repository has examples of broken patterns in ASP.NET Core applications
delimited
embassy - Modern embedded framework, using Rust and async.
config-rs - ⚙️ Layered configuration system for Rust applications (with strong support for 12-factor applications).
telepathy-qt - Telepathy Qt bindings
wg-async - Working group dedicated to improving the foundations of Async I/O in Rust
cap-std - Capability-oriented version of the Rust standard library