Ivy datasources: bottle neck

Hi

The number of max connection that suits best is depending on the project and the number of concurrent users. It is therefore not easy to define a good default value that suits all problems well. If you see bad performance use our VisualVM Plugin. There you see how many database connection are currently in use and what are the response times of the databases. If the number of database connection is almost at the maximum it is appropriate to increase the maximum.

Note, that it might be counterproductive to increase the maximum database connection to a high value, since each connection consumes resources on the database server.

Also have a look at the list with the slowest SQL statements. If a statement needs more than a second to execute it, it is worth to analyse the statement and try to optimize it. Note, that a database connection is reserved by a SQL statement. The longer a statement takes to execute the longer a database connection is reserved and meanwhile cannot be used by other request threads. Sometimes an additional index on a table column can boost performance by a factor of 1000. Especially if you have a lot of rows. Use database tools to explain how the SQL Statement is executed and find out if indexes are used to execute the statement or not.

For more information about our VisualVM Plugin see here: VisualVM Plugin