I'm facing a very weird behavior, trying to scale up vertically, running multiple Verticles
When I deploy in my local machine I can see the multiple Verticles and event-loop threads are created
[] | 2022-06-01 13:29:10.533 [vert.x-eventloop-thread-2] INFO Async-flow-http-proxy running......
[] | 2022-06-01 13:29:10.534 [vert.x-eventloop-thread-4] INFO Async-flow-http-proxy running......
[] | 2022-06-01 13:29:10.534 [vert.x-eventloop-thread-3] INFO Async-flow-http-proxy running......
[] | 2022-06-01 13:29:10.535 [vert.x-eventloop-thread-1] INFO Async-flow-http-proxy running......
[] | 2022-06-01 13:29:10.535 [vert.x-eventloop-thread-4] INFO Async-flow-http-proxy running......
[] | 2022-06-01 13:29:10.536 [vert.x-eventloop-thread-7] INFO Async-flow-http-proxy running......
[] | 2022-06-01 13:29:10.536 [vert.x-eventloop-thread-7] INFO Async-flow-http-proxy running......
Then when I run some queries I can see that all event-loops are used in round-robin fashion.
[] | 2022-06-01 13:29:11.126 [vert.x-eventloop-thread-2] INFO AsyncFlowHttpProxy - Calling next service localhost on port 8091
[] | 2022-06-01 13:29:11.127 [vert.x-eventloop-thread-4] INFO AsyncFlowHttpProxy - Calling next service localhost on port 8091
[] | 2022-06-01 13:29:11.127 [vert.x-eventloop-thread-6] INFO AsyncFlowHttpProxy - Calling next service localhost on port 8091
[] | 2022-06-01 13:29:11.126 [vert.x-eventloop-thread-0] INFO AsyncFlowHttpProxy - Calling next service localhost on port 8091
But, when I deploy in Kubernetes, and run the container with Java 11, and cpu '10'. I can still see that the multiple event-loops are created, but when I run request, only two of them are working, so then with big traffic I start struggling with only two event-loops
[] | 2022-06-01 13:29:11.126 [vert.x-eventloop-thread-2] INFO AsyncFlowHttpProxy - Calling next service localhost on port 8091
[] | 2022-06-01 13:29:11.127 [vert.x-eventloop-thread-4] INFO AsyncFlowHttpProxy - Calling next service localhost on port 8091