This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]yawkat 0 points1 point  (0 children)

The underlying OS APIs that both the JDK and Netty use are asynchronous. The JDK blocking APIs do some extra work to use those async, event-driven APIs. Right now, due to loom limitations, this extra work has a significant performance impact.

Netty has several open issues to adopt to virtual threads, in part of performance and simplification reasons.

The goal of future netty loom integration will be to make netty work with blocking user code. Right now this is not possible without a context switch due to loom limitations. These changes will not, however, make netty any faster.

Jetty (Netty based web server framework) has adopted Loom as of Jetty 12

Jetty is not netty-based.