[
https://issues.apache.org/jira/browse/POOL-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated POOL-410:
-----------------------------
Fix Version/s: 2.13
> EHN Max Concurrent Connections in Stats
> ---------------------------------------
>
> Key: POOL-410
> URL: https://issues.apache.org/jira/browse/POOL-410
> Project: Commons Pool
> Issue Type: Improvement
> Reporter: Thomas Freller
> Priority: Major
> Fix For: 2.13
>
>
> For tuning the Database the max concurrent used connections wold be relay
> great.
>
> So I could monitor the max concurrent connections of my pool and could see if
> I have to size up/down the max database connections (that can me memory
> intensive) or if I could downsize the Pool and also the Database i could save
> Memory and costs. At the Moment the only Indicator is
> maxBorrowWaitDuration=PT3.016S,
>
> But this can only tell me hat at the Moment the pool reached its max (because
> I set maxTotal to 1) my normal Case is to have up to 20 Pools of different
> Applications that connect to one instance of MariaDB and the output of
> maxBorrowWaitDuration is 0. So I only know I would be able to downsize the
> pool but I have no hint how to size the pool best.
> This Statistical Data should be also printed in the toString() Method.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
