nntp-rs
glommio
nntp-rs | glommio | |
---|---|---|
2 | 29 | |
26 | 2,866 | |
- | 2.0% | |
2.6 | 7.6 | |
over 2 years ago | 2 days ago | |
Rust | Rust | |
MIT License | GNU General Public License v3.0 or later |
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.
nntp-rs
-
Is async runtime (Tokio) overhead significant for a "real-time" video stream server?
Not for UDP servers, but I built something like this for TCP. See the SO_REUSEPORT code and the executor per thread code from my NNTP server project (which I no longer work on, I don't run NNTP servers anymore - the Rust server was up in #3 of the NNTP servers in the world at some point though, pushing 10s of Gbit/sec).
-
Setting up a local only NNTP server to collaborate in a group?
I was intrigued, so I did a search for a modern NNTP server. This one looks promising: https://github.com/miquels/nntp-rs. A WIP, but sounds like it can handle all READER commands.
glommio
-
I want to share my latest hobby project, dbeel: A distributed thread-per-core nosql db written in rust
I used glommio as the async executor (instead of something like tokio), and it is wonderful. For people wondering whether it's "good enough" or to use C++ and seastar (as I have thought about a lot before starting this project), take the leap of faith, it's fast - both in terms of run time and to code.
-
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.
-
Learning Async Rust with Too Many Web Servers
I think you missed one which is based on io_uring [1].
In my benchmarks with a slightly tweaked version it was 2x faster than Nginx and and 30x faster than Python's SimpleHttpServer.
[1] https://github.com/DataDog/glommio/blob/master/examples/hype...
-
How much reason is there to be multi-threaded in the k8s environment
b) It's proven now e.g Seastar, Glommio that the fastest way to run a multi-threaded application is to have one instance with one thread pinned per CPU core. Then to have fibers/lightweight threads on top handling all of the asynchronous code. Your approach of lots of instances is the slowest so there will be a ton of unnecessary thread context-switching.
-
Why does Actix-web's handler not require Send?
I assume Tokio itself, see e.g monoio or glommio, but also Seastar for C++.
-
How does async Rust work
https://github.com/DataDog/glommio Rust thread per core library.
-
Use io_uring for network I/O
> Few of us have really figured out io_uring. But that doesn't mean it is slower.
seastar.io is a high level framework that I believe has "figured out" io_uring, with additional caveats the framework imposes (which is honestly freeing).
Additionally the rust equivalent: https://github.com/DataDog/glommio
-
Is async runtime (Tokio) overhead significant for a "real-time" video stream server?
This use case is perfect for https://github.com/DataDog/glommio which is a thread-per-core runtime that is appropriate for latency sensitive code.
-
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
-
Building a High-Performance DB Buffer Pool in Zig W\ Io_uring New Fixed-Buffers
FYI, Datadog has a Rust library for scheduling things to run thread-per-core with io_uring
It'd be really useful for DB use cases:
https://github.com/DataDog/glommio
What are some alternatives?
nntp-proxy - simple NNTP proxy with SSL support
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
Jitsi Video Bridge - Jitsi Videobridge is a WebRTC compatible video router or SFU that lets build highly scalable video conferencing infrastructure (i.e., up to hundreds of conferences per server).
tokio-uring - An io_uring backed runtime for Rust
sydent - Sydent: Reference Matrix Identity Server
Seastar - High performance server-side application framework
monoio - Rust async runtime based on io-uring.
MIO - Metal I/O library for Rust.
actix-web - Actix Web is a powerful, pragmatic, and extremely fast web framework for Rust.
shadowsocks-rust - A Rust port of shadowsocks
dragonfly - A modern replacement for Redis and Memcached