Connections warming up about reactor-netty HOT 4 CLOSED

@Brieux1 You wrote that you did some warmup (several requests), but is it enough to fill the connection pool in order to be ready to handle the load?
Is it possible that with the first run, what you see is actually filling the connection pool i.e. establishing connections to the remote system, while with the second run the connection pool contains already connections ready to handle the load.

from reactor-netty.

Thank you for the response.
After some new tests, it appears that if we stop the 1st run after 20sec, then it is sufficient to handle the 2nd run.
Also if we extend the duration of the rampup to 40sec, then the application is able to handle all requests of the 1st run properly.

My misunderstanding was about the connection pool filling that was done during the first seconds of the 1st run (over 3k requests handled) that failed to handle the following requests (of the 1st run).
So at that point, the application can actually handle the load if we can manage to ensure a clean rampup (i.e. ensuring a connection pool filling before routing all the requests to the application).

Do you confirm that there is no possibility to programmatically initialize that connection pool?

from reactor-netty.

@Brieux1 Currently we do not expose configuration for warm up the connection pool. This is mostly because the load balancer etc. have aggressive idle timeout, so in real production scenario, even if you warm up the connection pool it is highly likely that the idle connections will be close very quickly.

from reactor-netty.

@Brieux1 I'm going to close this. For the time being there are no plans to expose a warm up functionality for the connection pool having in mind the reasons that I shared above.

from reactor-netty.