Page Comparison

Run deployPackager and obtain timing data on the complete workflow. You may want to run it multiple times, with different types of scripts packaged in different folders.

...

Overview

Below are suggestions that can improve packager performance.  Which suggestions may be most relevant can depend on which stages of packager are showing longer times spent in the packagerReport.html  (the packager reports are in the "Reports" directory structure of your Datical project).  You can see in the packagerReport.html how long each aspect of deployPackager takes:

Image Removed

Below are suggestions that can improve packager performance.  Which suggestions may be most relevant can depend on which stages of packager are showing longer times spent in the packagerReport.html and/or which packaging folders are showing longer times spent.  Our tech support team can assist you with looking at timing for different stages of packager and/or different types of scripts and making recommendations about which suggestions may be most appropriate for your environment. 

Note that although turning off certain features and settings can improve performance time, it can be a trade off since you may lose functionality.  Which features and settings are important to enable or disable may be different for each customer.and/or which packaging folders and script types are showing longer times spent.  The first step is to look in your packager reports to see which stage(s) of packaging are taking the most time.

Note that although turning off certain features and settings can improve performance time, it can be a trade off since you may lose functionality.  Which features and settings to narrow down the scope of or disable may be different for each customer.

Please contact our Technical Support team if you would like assistance analyzing the timing shown in your packager reports and adjusting the settings that are relevant for your environment.

Timing in packagerReport.html

First run deployPackager and obtain timing data on the complete workflow in the packagerReport.html. You may want to run packager multiple times, with different types of scripts committed in different folders.  The timing will likely be different for some types of scripts compared to others because packager uses different processes.  Such as timing for ddl folder (when using the default ddl packageMethod=convert) versus timing for sql_direct folder (uses packageMethod=direct) versus timing for function/procedure/etc stored logic folders (uses packageMethod=storedlogic).

Each packagerReport.html has six main sections:

• Overview - Scripts Processed
• Additional Logs & Reports
• Deploy Packager Phases
• Runtime Environment Properties
• Packager Configuration Properties
• All Properties

Here is an example of the whole report:

Image Added

For analyzing performance timing look at the third section called Deploy Packager Phases.  The Deploy Packager Phases section breaks down the timing for each stage of packager.  The phases are:

• Initialization
• Detect Files to Package
• Verify Metadata Properties
• Run SQL Rules
• Back up database
• Package Files
• Restore Database
• Final Forecast
• Final Deploy
• Archiving DDL and DML scripts
• Final checkin

Here is an example of only the Deploy Packager Phases section, showing the timing for each stage of packager:

Image Added

Items that can affect Packager Performance

1. When managing multiple schema in a multischema project, use the optional "schemaName" property in the metadata.properties file.  Here are details about it:

...