- Performance Tuning
In this guide you fill find basic advice for performance tuning of your Helidon application. Most of them target Netty tuning, as Helidon is based on it. You should also consider configuring/tuning Java heap size as per any Java application.
Configure Netty worker thread pool size
The Netty worker thread-pool is what handles your incoming requests. It defaults to 2*NCPU. To set it to something else you can set worker-count in resources/application.yaml:
server:
port: 8080
host: 0.0.0.0
worker-count: 2content_copy
Configure Netty’s maxOrder (Helidon 2.4.1 or earlier)
In some situations Netty can aggressively allocate memory per request. This has been addressed in recent versions of Helidon and Netty, but if you are running an earlier version set this system property when you start your Helidon application:
-Dio.netty.allocator.maxOrder=6content_copy
You can try smaller numbers.