tokio-stream-multiplexor-fork
| Crates.io | tokio-stream-multiplexor-fork |
| lib.rs | tokio-stream-multiplexor-fork |
| version | 0.5.8 |
| source | src |
| created_at | 2022-11-26 10:41:47.936588 |
| updated_at | 2023-01-20 08:46:23.540063 |
| description | Stream Multiplexor for tokio with a tcp like interface |
| homepage | |
| repository | https://github.com/GothAck/tokio-stream-multiplexor |
| max_upload_size | |
| id | 723199 |
| size | 89,759 |
(daibo83)
documentation
https://docs.rs/tokio-stream-multiplexor
README
Tokio Stream Multiplexor
TL;DR: Multiplex multiple streams over a single stream. Has a TcpListener / TcpSocket style interface, and uses u16 ports similar to TCP itself.
[dependencies]
foo = "1.2.3"
Why?
Because sometimes you wanna cram as much shite down one TCP stream as you possibly can, rather than have your application connect with multiple ports.
But Whyyyyyy?
Because I needed it. Inspired by async-smux, written for Tokio.
What about performance?
Doesn't this whole protocol in a protocol thing hurt perf?
Sure, but take a look at the benches:
throughput/tcp time: [28.968 ms 30.460 ms 31.744 ms]
thrpt: [7.8755 GiB/s 8.2076 GiB/s 8.6303 GiB/s]
throughput/mux time: [122.24 ms 135.96 ms 158.80 ms]
thrpt: [1.5743 GiB/s 1.8388 GiB/s 2.0451 GiB/s]
Approximately 4.5 times slower than TCP, but still able to shovel 1.8 GiB/s of shite... Seems alright to me. (Numbers could possibly be improved with some tuning of the config params too.)