Page Comparison

<repoName>.metaservice.type=databasev2
<repoName>.metaservice.databasev2.driver=
<repoName>.metaservice.databasev2.url=
<repoName>.metaservice.databasev2.user=
<repoName>.metaservice.databasev2.password=
#<repoName>.metaservice.databasev2.read-connections.max= #default: 32, not after 2.7.0
#<repoName>.metaservice.databasev2.read-connections.min= #default: 32, not after 2.7.0
#<repoName>.metaservice.databasev2.read-connections.shared= #default: false, not after 2.7.0
#<repoName>.metaservice.databasev2.write-connections.max= #default: 32, not after 2.7.0
#<repoName>.metaservice.databasev2.write-connections.min= #default: 32, not after 2.7.0
#<repoName>.metaservice.databasev2.cache-statements= #default: false, not after 2.7.0
#<repoName>.metaservice.databasev2.cache-statements.size= #default: 50, not after 2.7.0
#<repoName>.metaservice.databasev2.minimumIdle= #default: 10 minimumPoolSize
#<repoName>.metaservice.databasev2.maximumPoolSize= #default: 10
#<repoName>.metaservice.databasev2.connectionTimeout= #default: 30000 time after when a request for connection lease will time out
#<repoName>.metaservice.databasev2.idleTimeout= #default: 600000 time after when idle connections will be closed
#<repoName>.metaservice.databasev2.keepaliveTime= #default: 0
#<repoName>.metaservice.databasev2.maxLifetime= #default: 1800000
#<repoName>.metaservice.databasev2.scripts= #default: classpath:sql/metav2/migration/h2|sqlserver|oracle, dependening on database provider , 3.0.0+

As of version 3.4.0 the connection pool handling was improved. It allows using a smaller number of connections, i.e. changing the parameter minimumIdle to 2 should lower the utitilization utilization of the database without significant impact on overall performance. (Local tests with 120 parallel threads and min and max set to 1 worked without error at a duration for a write with 200ms)