| Table of Contents |
|---|
...
- Please see the notes in these pages:
- Performance recommendations:
- If you do not review or use the information in the Stored Logic Validity Check section of your deploy reports, then set storedLogicValidityCheck="disabled" to avoid possible performance slow down for a feature you aren't actively using.
- If you review and use the Stored Logic Validity Check information in your deploy reports but you do not use the storedLogicValidityAction=FAIL option, then we recommend setting storedLogicValidityCheck="limited".
- If you review and use the Stored Logic Validity Check information in your deploy reports and you also have enabled the storedLogicValidityAction=FAIL option, then we recommend setting storedLogicValidityCheck="local". (This is the default setting.)
- Although storedLogicValidityCheck="global" is an available setting and is the most comprehensive, if performance timing is an important consideration then it may be better to use a smaller scope such as "local" or "limited".
...
Please see the instructions on this page: Increase the amount of RAM used by Datical DBLiquibase Enterprise
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 Status, statusDetails, and Pipeline Status 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 This also improved operations which run status implicitly (CLI & GUI) - All types of 'deploy' operations, All types of 'rollback' operations, Deploy Packager, Convert SQL, and Change Log Syncsuch as deploy, rollback, deployPackager, convert SQL and changeLogSync.
- There were improvements for memory utilization of SQL scripts that produce a high-volume output in 7.11 (and higher).
- There were improvements for SQL Parser for Oracle in version 7.12 and 7.8 (and higher). If you are using SQL Parser for Oracle, we recommend running a recent 7.x version.
- There were improvements for Limited Forecast in version 7.13 (and higher). Areas where you may notice performance improvements:
- Limited Forecast will only profile tables impacted by the changesets to be forecasted or deployed
- Limited Forecast will only profile the schema impacted by the changesets to be forecasted or deployed in multi-schema projects
- Significant performance improvements for Forecast profiling in version 7.14 (and higher):
- Faster forecasting of Views and Materialized Views
- Faster profiling for tables, columns, and views in multi-schema projects
- Use multiple connections (maximum of 10 connections) to profile schemas simultaneously in Oracle multi-schema projects. Note that with 7.14 (and higher) in Oracle projects with multiple schemas, you may notice higher CPU utilization due to multiple connections being used for Oracle forecast profiling.
There are other performance improvement suggestions on these pages:
...