Multiple rest client instances

[ichrist-gr]

Hello all,
I have an application that sends loads of http requests in another service. Performance concerns us, so we decided to use vertx multiple verticle instances, to perform these requests. But as far as i understand, all these verticle instances (10) use the same rest client instance, so we see no performance benefit.

How can i overcome this issue and inject multiple rest client instances (one per each verticle instance)

Thank you very much.

[quarkus-bot[bot]]

/cc @Sgitario, @cescoffier, @geoand

[ichrist-gr]

I should also include that we are using the reactive libraries for resteasy and rest client and we have registered the config for connections:
connection-pool-size: 10

[geoand]

Hi,

Performance concerns us, so we decided to use vertx multiple verticle instances, to perform these requests

Can you describe your performance concern and what your thought process on using multiple verticle instances was?
I want to understand the root cause before trying to give an answer.

Thanks

[geoand]

I am still unclear of where you think the performance problems are

[ichrist-gr]

Sorry for confusing you george.
The way it is right now, each batch of 50 events will be finished in 1 minute.
So when invoking the service for each event (taskService.processTask) it's journey demands 4 api calls.
So we assume that if we wrap the taskService.processTask into a verticle and scale up this verticle with 10 instances, each event will be processed in different event loops.
Will this assumption be an actual performance increase or am i getting something wrong?

In fact, we want to achieve a parallel execution for the event sublists.

Thank you very much

[geoand]

@cescoffier can tell you more for sure, but AFAIK, it won't make a difference. If I were you, I would increase quarkus.rest-client.myclient.connection-pool-size.
If that does not increase the performance of the system, you'll probably have to introduce tracing to figure out what's going on.

[cescoffier]

If you use a single rest client - you won't see any benefit, because it will use a single event loop.

If you use a web client, then, using verticles could work. It will depends on the number of core. 10 verticles would require 10 cores, or you will overcommit.

As said by @geoand, I would recommend increasing the number of connection and keep thing simple. Observe and measure before going to direction that may not bring any benefits.

[ichrist-gr]

Thank you for your time guys!!

[ichrist-gr]

Returned with some results. Indeed guys playing around with the connection pool size and benchmarking every time, ended up in a performance increase. (Other's system gateway started rejecting me because of heavy load😇).

Thank you very much!!!

[geoand]

Great to hear that the Quarkus bottleneck was eliminated :)