search

rundeck / docs

Rundeck documentation
https://github.com/rundeck/rundeck
68 stars 146 forks source link

Tuning missing DB information #777

Open pwonson opened 3 years ago

pwonson commented 3 years ago

Describe the bug Information on the bottle neck which can be caused by the database backend should be added.

@ProTip notes as follows

This is also conspicuously missing from the tuning guide but they will also want to increase the data source maxActive to as high as their database can handle for this type of load testing..

dataSource.properties.maxActive

@jgarces-pd also has good DB tuning advise (please add)

Source page https://docs.rundeck.com/docs/administration/maintenance/tuning-rundeck.html#tuning-rundeck

jgarces-pd commented 3 years ago

most of these properties can be configured adding the dataSource. prefix, and some of them are specifically from each jdbc driver:

http://tomee.apache.org/datasource-config.html

Some of those configs like maxWaitTime and maxIddle has default values preconfigured (can be confirmed seeing the system report view), but those can be improve sometimes the connection.

@cwaltherf do you have any other properties that should work too?

cwaltherf commented 3 years ago

@jgarces-pd according to the use cases I have seen so far this looks fairly complete.

ProTip commented 3 years ago

I would recommend as a baseline "rule of thumb" that the max connections be set to 3x the number of quarts threads:

100 quarts threads X 3 = 300 max connections.