Netty version embedded in a dedicated Quarkus version ? #55611
Replies: 1 comment
|
On Quarkus 3.x, we use Netty 4.1. On Quarkus 4, we use Netty 4.2. But to answer your question, it depends. If you use a compatible version AND you handle event loop correctly (no blocking), you can use our Netty and reuse the same event loop. That is the most efficient. If you use a compatible version BUT use event loops in a more funky way or require bootstrap adaptation, you can use our Netty but don't reuse our event loop. Unfortunately, you will have to take that into account when configuring the number of event loop, as you do not want to overcommit on the number of CPU core. If you use an incompatible version, you need to shade it. Be aware that native compilation will be challenging in this case. As, like for the previous case, sizing the event loop groups can be challenging. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hello,
I know that Netty is used by Quarkus as foundation layer.
How do we know which Netty version is included in a dedicated Quarkus version?
Or we can use any Netty version for a dedicated Quarkus version ?
Best Regards.
All reactions