tsyncp
flume
| tsyncp | flume | |
|---|---|---|
| 1 | 14 | |
| 33 | 2,200 | |
| - | - | |
| 0.0 | 3.9 | |
| about 2 years ago | 14 days ago | |
| Rust | 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.
tsyncp
-
Tsyncp: Channel-like primitives (mpsc, broadcast, etc) over TCP
tsyncp is a simple library that provides channel-like primitives (mpsc, broadcast, etc) over TCP.
flume
-
Hyperbridge: Fast multi-producer, multi-consumer unbounded channel in Rust
The repository seems abandoned; or maybe complete?
At work we use flume, which is another capable multi-producer, multi-consumer async-capable channel [1]. It's great for shuffling data between threads, as well as between async tasks, and between threads and async tasks. Basically any time you want to pieces of code to exchange data or signals without pesky shared state.
1: https://github.com/zesterer/flume
- pub/sub Event bus in rust
-
Is there any part of the Standard Library that really impresses you?
I also like flume, it has impressive performance (although not the best). More importantly, it's written only with safe rust. https://github.com/zesterer/flume
-
appreciating fearless concurrency
The most commonly suggested replacement for mspc is crossbeam-channel; flume is also relatively popular.
-
Rust has a small standard library (and that's ok)
It's not officially deprecated, but the alternatives on crates.io are considered better. flume and crossbeam-channel feature less unsafe code and offer better performance. Benchmarks.
-
Why are so many important features not in standard library yet?
it's slow (checkout flume's benchmarks for example)
-
Request-response communication between threads?
I would have done the same. I think, and I might be wrong, but the only other alternative, besides anything unsafe, would be to pass mutex back, but I am not sure this would be faster. Btw, I have not done testing, but you might want to look at Flume for your mpsc channels: https://github.com/zesterer/flume Flume, seems to be very fast mpsc implementation. I am planning to evaluate it for logging system.
-
A mini-Erlang/Elixir -- tell me if/why my idea sucks
For concurrency/parallelism, you launch at most 2 * CPU Cores, PIN them and use a fast broker to spread the task (like a ring buffer or an MPSC). But you keep linear scan, tight loops, SIMD friendly data, on each. You are not switching context that much, and instead, bet you will process the batch fast. (CPUs are fast today!)
- Whats your favourite open source Rust project that needs more recognition?
-
Suggestions on a fast spmc architecture.
https://crates.io/crates/flume and https://crates.io/crates/crossbeam-channel provide MPMC channels.
What are some alternatives?
loole - A safe sync/async multi-producer, multi-consumer channel
uniffi-rs - a multi-language bindings generator for rust
remoc - Remoc 🦑 — Remote multiplexed objects, channels and RPC for Rust
rust - Empowering everyone to build reliable and efficient software.
Cargo - The Rust package manager
async-wormhole
bevy - A refreshingly simple data-driven game engine built in Rust
trust-dns - A Rust based DNS client, server, and resolver [Moved to: https://github.com/hickory-dns/hickory-dns]
reqwest - An easy and powerful Rust HTTP Client
rust-cli-boilerplate - Rust project boilerplate for CLI applications
Rustlings - :crab: Small exercises to get you used to reading and writing Rust code!
trantor - a non-blocking I/O tcp network lib based on c++14/17