connection pool same-context enforced option

[franz1981]

It would be great an option to enforce acquisition of connections just from the same context, for maximum performance or been parked if not found any; together with some telemetry to measure both latencies to acquire leases and miss/hit/release/wait/resume counters to measure effectiveness. This would help both as a proper option and to check what's the advantage of stealing connections that belong to another context.

[franz1981]

I am just sad that if we just want to pick connection from the same context probably we don't need a combiner executor but we could just use per-context (and single threaded) stacks/queues and same for waiters; and a global max connections counter (using compareAndSet to modify the shared count)

The combiner instead can be used to trigger periodic randevouz to rebalance connections count/shares.
@vietj

[vietj]

in that case, the pool should not be shared and remain confined in a verticle with several pools.

…

On Sat, Apr 22, 2023 at 4:37 PM Francesco Nigro ***@***.***> wrote: I am just sad that if we just want to pick connection from the same context probably we don't need a combiner executor but we could just use per-context (and single threaded) stacks/queues @vietj <https://github.com/vietj> — Reply to this email directly, view it on GitHub <#1317 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABXDCQI4OTQUSR2TJWLKFDXCPULTANCNFSM6AAAAAAXH36F5U> . You are receiving this because you were mentioned.Message ID: ***@***.***>