Have an investigation on the Monoio runtime? about ntex HOT 7 OPEN

The implementation zzau13@e4aced3, but has some problems:

• need nightly and I have no idea how to put it only to compile in nightly, so that ntex in stable does not compile.

from ntex.

i dont have time at the moment

from ntex.

how is performance?

from ntex.

how is performance?

Well, I was still reviewing the implementation before putting it in the techempower benchmark environment. I don't know if I'll have time today.

Also with this change ntex only compiles in nightly and I don't see a way to include a dependency according to the version of Rust.

from ntex.

@botika You can conditionally apply a feature that runs only on nightly.

from ntex.

@botika In case you haven't seen these, I found a couple of online answers about how to conditionally compile a feature only for nightly. They are from 2019, so the syntax may have evolved or changed (I haven't personally tried them):

https://stackoverflow.com/questions/59542378/conditional-compilation-for-nightly-vs-stable-rust-or-compiler-version
https://users.rust-lang.org/t/add-unstable-feature-only-if-compiled-on-nightly/27886

from ntex.

The benchmark is misleading. If you look at the source it compares multi-threaded tokio with thread per core glommio and monoio. Which is not how ntex work under the hood with tokio. Besides that the bench does not include abstraction over poll based api which ntex uses internally. And the cost of converting a completion future to a readiness future soundly can be high.(depend on the implementation)
From my personal test I don't find io_uring suitable for network io handling in Rust (yet).

from ntex.