TechEmpower just released their latest round (19) of their server middleware benchmark. You can check the results here: https://www.techempower.com/benchmarks

Ktor is 219th, about halfway down the list. 😬

Performance is not everything… for some scenarios half the performance is good enough, for others it only means you pass from 1 instance to 2… Maybe you need that peak performance only for one or two of your services. So you shouldn’t compromise productivity on the other modules. At least for me, it is more important to pick the tool more suit for the job, than to select “the best” one and stick to it no matter what :)

Are there any people using this drogon or it is developed only to win such competitions?

Drogon is c++ based Actix is Rust You'll notice that the fastest ones have async/await support (aka coroutines) and use them properly.

@kenkyee I do understand that. The comparison looks like "C/Rust is fast and Java is slow", but actually it is not. You can see that wizzardo's engine is at the top, but one need to remember that main difference of wizzardo-http is that it fixes linux problem with async io. So it is not about lanugage, it is about OS optimization. And if we run those examples on Windows, the results could be quite different (It had async io suuport for a long time).

Vertx beats most Java frameworks and has always been in the top 10. Uses async await concept too

Yeah. I mean that if we look at Ktor it is not that up the winner lists, but it relies on on Java-nio so it is quite possible that it is not that fast because java-nio lacks optimizations for linux. Also I agree, that those comparisons are useless in the real life.

AFAIK, vert.x also relies on NIO. It's an old time tested framework though...

But there are other java/kotlin frameworks near the top. Jooby, http4k, ratpack, hexagon, micronaut, dropwizard.. most of them not using reactive model

Reactive model is important for disk IO, otherwis it is not that important.

or network io, or db io, or any io. but still, non reactive apps in the java world, written well, perform very very good

Of course. Reactivity is a compromised term. We should call it asynchronous. Usually you want your code to be asynchronous to avoid thread blocking, but you can do that with good old callback style. Tools like coroutines just make it simpler. By the way, ktor io core is not based on coroutines, it is a classic blocking API.

Someone should provide a Drogon intregration with Kotlin Native… It could be Drokon (or Drokot)

why do you think that ktor core is blocking? its definately not.

I said IO core. Unless they changed something dramatically since kotlinx-io fork, operations on Input and Output are blocking.

and IO being socket IO?

This one: https://github.com/ktorio/ktor/tree/master/ktor-io

seems it can do blocking and non blocking

There are no callbacks so it uses nio in a blocking way. I am not saying that there should be necessary blocking code, I just say that it is not necessary non-blocking.