You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
The text was updated successfully, but these errors were encountered: