monoio VS smol

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...

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.

I assume Tokio itself, see e.g monoio or glommio, but also Seastar for C++.

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.

I believe this is also "thread-per-core".

Bytedance has their in-house monoio <https://github.com/bytedance/monoio> (supports io-uring) but it requires rust nightly.

There's another thread-per-core runtime called https://github.com/bytedance/monoio

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

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

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.

There is also https://github.com/smol-rs/smol which has components which you can compose into your own executor if you still need async IO but your usage patterns don't fit into the general purpose ones that Tokio provides.

If you need precise control over scheduling, consider building something on top of https://github.com/smol-rs/smol

Tokio is a "take what you need" framework, whilst Async-std started as an "everything the box" solution. Today both have a lot of crossover with micro async runtimes like smol becoming the foundation one of framework and optionally usable in the other. The ability to rip out a small dependent sub-crate (dependent package) like smol and use it independently with ease never get's boring, by the way. It's great way to include a test runtime in an async library without forcing the inclusion of a giant async framework.

Helix uses tokio. smol might be a good alternative however.

No, still active on GitHub. What gave you that idea? https://github.com/smol-rs/smol

Found the issue in Google cache. I'm not sure it's really fair of me to post this link here, but equally I think it's better to give the actual text rather than leave it vague.

https://webcache.googleusercontent.com/search?q=cache:PRjMyv...