3 ms·
Here are some performance tests comparing Quarkus to Python, Spring, and Payara (JEE) https://github.com/rmh78/quarkus-performance https://github.com/rmh78/qua
by vips7L 6y ago
Here are some performance tests comparing Quarkus to Python, Spring, and Payara (JEE)
https://github.com/rmh78/quarkus-performance https://github.com/rmh78/quarkus-performance
- jacques_chester 6y agoThis is impressive work, thankyou. Do you know when you might add a GraalVM Native version of the Spring examples?
- vips7L 6y agoThis is not me sorry. Just something I found.
- ralala 6y agoIt's a bit unfair to compare with synchronous python. Better: FastAPI, aiohttp, Quart,....
- vips7L 6y agoBut then shouldn't we also do non-blocking Java? Vert.x, webflux, akka-http? I also didn't make the bench marks.
- funcDropShadow 6y agoAt first glance, this benchmarks seem way to short to for JIT-compiled JVMs to reach steady state. I suspect the high cpu-usage comes from the jit compiler and decreased cache effectivity. I've seen JVMs needing 20 minutes to reach a steady state under load. But then, they've inlined your log configuration throughout the code, quite impressive, imho.
- vips7L 6y agoI THINK the author meant it to show time to first request (startup) and how fast you can handle X requests from start, due to Quarkus being focused on k8s/lambda. I personally prefer the JIT over native compilation.