At 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.
I 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.
It's a bit unfair to compare with synchronous python.
Better: FastAPI, aiohttp, Quart,....
But then shouldn't we also do non-blocking Java? Vert.x, webflux, akka-http?
I also didn't make the bench marks.
This is impressive work, thankyou. Do you know when you might add a GraalVM Native version of the Spring examples?