Pinot is a rest API that can support high QPS, what benefits are you looking into a connection pool? Connection pooling would likely be a threading configuration from your java service http client.

Thx for your replay, I think connection pool can support high qps with little threads, but pinot don’t support , we can just use thread pool in service code right?

Connection pool make sense for a stateful protocol like jdbc or raw tcp. HTTP is stateless. What you have on the server is HTTP listeners thread pool that answer client commands. You can scale those by adding more pinot brokers. That’s nothing else than regular a Jetty web server. Pinot is designed to serve high QPS with ( > 100k / sec) stateless http commands. If you introduce a thread pool on the client side, you will only create a potentially bottleneck in your client code. You can create as many concurrent http client threads against Pinot. The only benefit of pooling on the client end is that you will control potential resource exhaustion from your client. You’ll be reusing threads, not tcp connections.

Hi Correct me if I'm in the wrong but from my understanding, using client side connection pooling allows to reuse connections, instead of reopening new sockets for every request For example, I can see that the

pinot-db

Python client does not do that and ~25ms are spent establishing a new connection for every request. In a tight loop where multiple requests have to be sent, this quickly adds up

You are actually right, you can shave on the http tcp connection with an http client lib that supports pooling.

Thanks for confirming @Daniel Lavoie 🙂