Understanding count of minimum idle connections to zero in connection pool
26111982Apr 25 2013 — edited Oct 15 2014Hi,
I would like to understand if there is any overhead of creating connections if we keep the minIdle to zero in a connection pool where the eviction thread is configured.
As per the understanding I have, it's the initial creation of connection to the database is expensive operation.In the case of connection pool,this is being done when the data source is instantiated initially and the connection objects are maintained till the data source is destroyed.
Please help me understand the behavior when the minIdle is made 0. Will it try to create a new connection when all the connections are evicted and cause an overhead than making minIdle >0.
Thanks in advance