From time to time certain settings need to be updated to improve Datical's deployment performance (see items 1 through 6 below).
...
Recommendations to improve Deploy performance
- Optimize your Project Settings by disabling features you don't use or by narrowing the scope of the features you do use.
- Increase the amount of RAM used by Datical
...
- .
...
- Upgrade to a newer version of
...
- Liquibase Enterprise/Datical.
Project Settings that improve deploy performance
Check your values of these Project Settings
1. enableRowCount=”false” ”disabled” or "approximate" → Settings for Collecting Row Counts
...
6. autoGenSQL=false → Disabling the Automatically Generate SQL setting can improve performance if you don't need it: Configuring Project SettingsThese settings can up changed from Datical GUI, or by using hammer set commands in the CLI, or by using the optional project_creator script. Notice the attributes near the end of this excerpt from the
How they look in your datical.project file
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
<dbproject:Project xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:dbproject="http://datical.com/db/project/1.0" name="dpe-datical-paymentmanager" storedLogicExternal="true" deployThreshold="stopOnError" runtimeCredentials="true" multiSchema="true" dbSchemaDefinition="project" schemaSelectionStep="PAMAND5" trackingSchema="DATICAL" storedLogicValidityCheck="limited" enableRowCount="approximatedisabled" limitForecastProfiling="true" deployMode="quick autoGenSQL="false" forecastDML="false"> |
How to Change the Project Settings
There are more details about each setting option on the Configuring Project Settings page. You can change them using the method you prefer:
GUI
In the Datical desktop client/Eclipse GUI, you would set the above mentioned settings Configuring Project Settings:
...
...
open your project, go to the Settings tab, and expand open the Deployment Settings section. Here is an example of what the settings would look like in the GUI when optimizing for performance:
Command Line
In the CLI, you can set those same items using "hammer set" commands for enableRowCount, limitForecastProfiling, deployMode, invalidsCheck, and autoGenSQL. Please see the set command details here: CLI Commands#set
Project Creator
If you use the optional project_creator script, you can set these settings when initially creating the project. Please see the instructions here: Creating a Datical Project Using the Project Creation Script (project_creator.groovy)7.
Increase the amount of RAM used by Datical
The default is -Xmx2048m. You can increase it to -Xmx4096m or -Xmx8192m.
Please see the instructions on this page: Increase the amount of RAM used by Datical DB8. Upgrade to a current
Upgrade to a newer version of Liquibase Enterprise/Datical
...
DB
- There were performance improvements to forecast for those who run forecast/deploy on Windows clients or Windows agents in Datical DB version 6.8 (and higher).
- There were performance improvements for those who use the Stored Logic Validity Check project setting in Datical DB version 6.12 (and higher).
- There were performance improvements for several operations in Datical DB version 6.14 (and higher). Areas where you may notice performance improvements:
- Status/Pipeline Status operations in the Datical DB GUI
- 'status' & 'statusDetails' commands in the CLI
- Complex operations which run status implicitly (CLI & GUI) - All types of 'deploy' operations, All types of 'rollback' operations, Deploy Packager, Convert SQL, and Change Log Sync
- There were improvements for SQL Parser for Oracle in versions 6.15, 7.6, and 7.8. If you are using SQL Parser for Oracle, we recommend running a recent 7.x version.
There are other performance improvement suggestions on these pages:
...