> On Apr 5, 2019, at 8:23 AM, Anthony Baker wrote:
>
> One question: if I’m using thread-local connections ho does that affect pool
> sizing? Are thread-local connections included in the overall pool size or
> accounted for separately?
On the client side thread local pool just pulls from t
Well articulated and a wise decision; Jake. +1
On Fri, Apr 5, 2019 at 8:24 AM Anthony Baker wrote:
> One question: if I’m using thread-local connections ho does that affect
> pool sizing? Are thread-local connections included in the overall pool
> size or accounted for separately?
>
> We may w
One question: if I’m using thread-local connections ho does that affect pool
sizing? Are thread-local connections included in the overall pool size or
accounted for separately?
We may want some explicit release notes if a user would need to resize their
pools during an upgrade.
Anthony
> O
Devs,
The current connection pooling implementation contains a setting that enables a
secondary pool that is thread local. See ClientCacheFactory.
setPoolThreadLocalConnections method for details. This thread local pooling was
added to reduce contention on the primary connection pool under high
