I really doubt that single vertx instance (vertice) is faster than single instance of libuv. Libuv is written in pure C and talks directly to system kernel (file descriptors). The main reason that vertx is faster is the multi-reactor pattern. Most of frameworks based on libuv (node, asyncio) are single threaded. Vertx can create event loop on each thread by default.
I'm Paulo and I've used my 10+ years of software development experience writing, rewriting, banging my head against the wall, editing and re-editing high-performance web application to make Vert.x ...
Hi Marek, please carefully read the benchmark source code. You will see that the node implementations are scaling to all cores using the cluster module. Also others had the same question and also provided a implementation using 0http which claims to be fast, results however show the opposite.
I really doubt that single vertx instance (vertice) is faster than single instance of libuv. Libuv is written in pure C and talks directly to system kernel (file descriptors). The main reason that vertx is faster is the multi-reactor pattern. Most of frameworks based on libuv (node, asyncio) are single threaded. Vertx can create event loop on each thread by default.
Hi Marek, please carefully read the benchmark source code. You will see that the node implementations are scaling to all cores using the cluster module. Also others had the same question and also provided a implementation using 0http which claims to be fast, results however show the opposite.
You can see all source code here:
github.com/TechEmpower/FrameworkBe...
Also the code has been peer reviewed but you're welcome to review it too.
The latest run and results are here:
techempower.com/benchmarks/#sectio...