Reduce Update Cycle Processing Time

Adobe Commerce Intelligence syncs with your database throughout the day to replicate new data, ensuring that your dashboards always show the latest information.

Many factors can add to an already lengthy update time. Certain replication methods, higher recheck frequencies, and the number of dashboards and charts are just a few contributors. This topics discusses some best practices to reduce your update times.

Decrease Recheck Frequency

In a database table, there can be data columns with changeable values. For example, in an orders table there might be a column called status. When an order is initially written to the database, the status column might contain the value pending. The order is replicated in your Data Warehouse with this pending value.

Changeable columns must be rechecked for updated values over time. By default, Commerce Intelligence rechecks these columns during every update, but if there is a large amount of data to be rechecked and replicated, it can negatively impact your update time. Instead of running rechecks during every update, Adobe recommends setting the recheck frequency to daily, weekly, or monthly.

Use Incremental Replication Methods

As mentioned above, long update times are directly correlated to how much data has to be rechecked and replicated. Incremental replication methods can greatly reduce the amount of data processed during the update cycle. Where possible, Adobe recommends using these methods or modifying your database to support an incremental method.

Remove Unused Charts from Dashboards

At the end of the update cycle, Commerce Intelligence performs a cache operation for all charts. A cache stores data so future requests for information can be completed faster. In Commerce Intelligence, this means dashboards load quickly because charts do not need to query data every time they load.

Since Commerce Intelligence only performs cache operations for charts found in a dashboard, removing unused charts from your dashboards decreases your update time. Keep in mind that the same chart might be on multiple dashboards - check with your team to make sure they also removed any unused charts.

Optimize Your Database for Analysis

In addition to reevaluating recheck frequencies, replication methods, and chart usefulness, you can also optimize your database for analysis.

Wrapping Up

If your update time still seems slow even after implementing these recommendations, contact the support team.