unikdahal commented on issue #4540:
URL: https://github.com/apache/arrow-adbc/issues/4540#issuecomment-5017721047
That's fair connection reuse can be layered on top; dropping the pool idea.
One narrower follow-up though: one of the dominant per-connect cost is
gRPC channel setup (TCP + TLS handshake), and that part an external pool can't
reach it lives inside `FlightSqlConnection`. Workloads needing many
*concurrent* connections (e.g. distinct per-connection session state) pay one
channel each, even though HTTP/2 is designed to multiplex exactly this over a
single connection sharing channels across stubs is standard gRPC guidance.
arrow-java ships `FlightGrpcUtils.createFlightClientWithSharedChannel` for
precisely this case.
Would an opt-in flag on the Flight SQL driver (default off, one shared
`ManagedChannel` per `FlightSqlDatabase`) be reasonable?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
