Several factors affect how many back-end sessions are needed for each database. Back-end sessions are started and stopped based on the loads of each database. So, if a database is heavily used, the server keeps more back-end sessions for that database. The server does stop excessive sessions when the load is not that heavy. The section describes which settings in the ccm.server.properties file can be changed to tune the number of back-end sessions the server uses. Many of these settings allow a global setting that sets the value for all databases, and a database-specific setting which only affect individual databases. When both settings exist for a database, the database-specific value is used.
The following settings can be configured. They govern the behavior of the back-end sessions managed by the CCM server.