To obtain the correct number for a connection Datasource pool, first, we may need to understand queue theory and have good observability of the data source itself and from there take decisions.
Said that I'd like to review once again the Little's law (from Queuing Theory)
L – average number of customers
λ – long-term average arrival rate
W – average time a request spends in a system
L : Número promedio de clientes en un sistema
λ : Número promedio de clientes que llegan al sistema por unidad de tiempo
W : Tiempo promedio de espera en un sistema
- https://vladmihalcea.com/2014/05/20/the-simple-scalability-equation/
- https://en.wikipedia.org/wiki/Little%27s_law
- https://www.gestiondeoperaciones.net/lineas-de-espera/que-es-la-ley-de-little-y-su-aplicacion-en-el-analisis-de-lineas-de-espera/
-
https://vladmihalcea.com/the-anatomy-of-connection-pooling/
- https://stackoverflow.com/questions/1208077/optimal-number-of-connections-in-connection-pool
- https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-Sizing
- http://xmlandmore.blogspot.com/2012/10/dynamically-sizing-jdbc-connection-pool.html
- https://vladmihalcea.com/2014/04/25/flexy-pool-reactive-connection-pooling/
-
https://vladmihalcea.com/2014/04/30/professional-connection-pool-sizing-with-flexy-pool/
