Tip Tuesday: Commerce/Config deployment performance suggestions

Summary:

Commerce/Config deployment performance suggestions.

Tuesday Tip😊

When it comes to Commerce and Configuration, deployments can start taking a longer amount of time once an implementation grows in size and age. There are several obvious factors that affect this performance: # of attributes, # of rules, etc. While optimizing these will result in some benefits, significant improvements won't be seen unless a large number of objects is reviewed.

There are two parts of the setup that will result in significant gains to Deployment performance:

1. Migration Packages (Config & Commerce) - With the way CPQ currently processes deployment data, all Migration Packages will be modified when a deployment is performed. This is to make sure that the latest data is available if a migration package is downloaded. In order to perform optimization in this case, remove any migration packages that are not actively used.